writing-specs-designs

SKILL.md

Framework-driven guidance for writing specs and design documents from seven product leaders.

Determine fidelity level upfront: low-fi sketches for alignment, high-fi specs for implementation details

Favor prototypes over static documentation; test the feel with real software rather than screenshots

Use fat marker sketches and breadboarding to avoid getting stuck on UI details like colors or spacing

Recognize that temporary design shortcuts often become permanent product decisions; design with long-term implications in mind

Optimize for efficiency in every interaction, especially mobile; each tap must provide immediate value to users

Writing Specs & Designs

Help the user write effective specs and design documents using frameworks and insights from 7 product leaders.

How to Help

When the user asks for help with specs and design docs:

Determine the fidelity level - Ask if they need conceptual alignment (low-fi) or detailed implementation guidance (high-fi)

Encourage prototyping over polish - Push toward functional prototypes where possible rather than static documentation

Focus on moving pieces - Help them identify the key affordances, connections, and system behaviors

Consider long-term implications - Remind them that temporary shortcuts often become permanent design decisions

Core Principles

Low-fidelity sketches drive collaboration

Christina Wodtke: "If I got on the whiteboard and drew really badly, somebody else will go, 'No, no, no, it doesn't work that way. Give me this pen.' It gets you so fast to a shared vision." Drawing 'badly' invites participation and corrections, accelerating alignment.