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 requires explicit confirmation of the brief before implementation begins.

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

No, this Skill explicitly does not write code. It operates only in the planning phase, producing a design brief that can be handed off to implementation skills such as /impeccable craft or any other build workflow.

Use discovery when the feature's users, success criteria, 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 complex states or dynamic content.

It produces planning artifacts only, not working code, so a separate implementation step is always required. It also depends on the /impeccable skill for design principles and context gathering, which must be available beforehand.