What problem does it solve? Jumping straight into code without a validated design leads to wasted work, unexamined assumptions, and features that miss user intent. This Skill enforces a structured discovery process so every feature, component, or behavior change starts from an approved design. ## Core Features & Use Cases - Context Exploration: Reviews existing project files, docs, and recent commits before asking questions. - One-Question-at-a-Time Clarification: Refines purpose, constraints, and success criteria through focused dialogue, preferring multiple-choice questions. - Approach Comparison: Proposes 2-3 alternative approaches with trade-offs and a clear recommendation. - Design Documentation: Writes the approved design to docs/plans/YYYY-MM-DD-<topic>-design.md, commits it to git, then hands off to the writing-plans skill. - Use Case: Before building a new API endpoint, use this Skill to explore requirements, compare architectural approaches, and produce an approved design doc before any code is written. ## Quick Start Ask the agent to brainstorm the feature you want to build, and answer its clarifying questions until it presents a design for your approval.
