shape

Run a structured discovery interview covering the feature's purpose, target users, content ranges, edge cases, and constraints, then synthesize the answers into a design brief. This Skill automates that process and produces a brief ready for implementation handoff.

A design brief should include a feature summary, the primary user action, design direction, layout strategy, key states (default, empty, loading, error), interaction model, content requirements, and open questions. This Skill generates all nine sections from interview answers.

No, this Skill is scoped to design planning only and explicitly does not write code. Its output is a design brief that can be handed to implementation skills such as /impeccable craft or any other build workflow.

Use discovery when the feature's users, content ranges, edge cases, or design direction are unclear. Skipping this step often leads to generic interfaces that miss the actual user need, especially for features with multiple states or dynamic content.

A design brief captures direction and strategy but not pixel-level specifications or working code. Implementers still resolve open questions during the build, and the brief's quality depends on how thoroughly the discovery questions are answered.