What problem does it solve? Turning a rough feature idea into a technical design often leaves open decisions, unverified assumptions, and scope ambiguity that surface mid-implementation. This Skill interviews the user until every material decision is closed, grounds the design in the actual codebase, and self-reviews the result before it ships. ## Core Features & Use Cases - Clarification interview: Iteratively asks questions covering scope, acceptance criteria, data models, interfaces, failure behavior, and cross-project contracts until no open decision remains. - Codebase grounding: Reads existing modules, prior designs, and storm documents, re-verifying inherited claims and path:line citations before designing against them. - Mockups and cross-project briefs: Renders a mockup for any unsettled user-visible surface and writes a self-contained design brief for each other project the feature spans. - Use Case: After brainstorming a reminders feature for a todo app, run the skill to produce a complete design document under features/feature-v<N>-<description>/ that /feature-plan can stage into a TDD implementation plan. ## Quick Start Ask the assistant to run /feature-design with a short description of the feature you want designed, or invoke it right after completing a /feature-storm brainstorm.