What problem does it solve? Jumping straight into code without a validated design leads to misaligned assumptions, scope creep, and costly rework. This Skill enforces a design-first workflow that explores user intent, constraints, and alternatives before any implementation begins. ## Core Features & Use Cases - Structured Discovery: Explores project context, then asks clarifying questions one at a time to understand purpose, constraints, and success criteria. - Approach Comparison: Proposes 2-3 alternative approaches with trade-offs and a reasoned recommendation before settling on a direction. - Incremental Design Approval: Presents the design in sections scaled to complexity, requiring explicit user approval before writing the design doc to docs/plans/ and transitioning to the writing-plans skill. - Use Case: A user says "let's add dark mode to the app." The Skill checks the current theme implementation, asks whether it should be automatic or manual, compares CSS variables vs. Tailwind dark classes vs. a theme provider, presents the design section by section, and only after approval writes the design document and hands off to planning. ## Quick Start Ask the assistant to help you design a new feature or change, for example: "Help me brainstorm and design a notification system for my app before we build it."
