What problem does it solve? Jumping straight into code on unexamined assumptions causes wasted work and rework. This Skill forces a structured discovery phase — exploring project context, asking clarifying questions one at a time, and presenting design alternatives — so every feature, component, or behavior change starts from a validated, written spec rather than guesswork. ## Core Features & Use Cases - Structured Discovery Dialogue: Explores current project state, then asks one question at a time (multiple choice preferred) to clarify purpose, constraints, and success criteria. - Design Presentation with Approval Gates: Proposes 2-3 approaches with trade-offs, presents the design in sections scaled to complexity, and blocks all implementation until the user approves. - Spec Authoring and Self-Review: Writes the approved design to a dated spec file under docs/nd/specifications, runs a placeholder/consistency/scope/ambiguity self-review, and hands off to the writing-plans skill only after user sign-off. - Use Case: Before building a new feature, invoke this Skill to surface hidden requirements, compare architectural approaches, and produce a committed design document that an implementation plan can be built from. ## 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.
