What problem does it solve? Starting to code from vague or ambiguous requirements leads to rework, misaligned implementations, and undocumented architectural decisions. This Skill enforces writing a validated specification before any code, so both the human and the AI share a single source of truth about what is being built and how success is measured. ## Core Features & Use Cases - Four-Phase Gated Workflow: Progresses through Specify, Plan, Tasks, and Implement phases, each requiring human review before advancing. - Structured Spec Template: Covers six core areas including objective, commands, project structure, code style, testing strategy, and Always/Ask First/Never boundaries. - Assumption Surfacing & Success Criteria: Forces explicit listing of assumptions and reframes vague requirements like "make it faster" into testable conditions such as LCP under 2.5 seconds. - Use Case: When asked to build a new dashboard feature with only a rough idea, use this Skill to interview the stakeholder, produce a spec document with acceptance criteria, break it into dependency-ordered tasks, and only then begin implementation. ## Quick Start Ask the agent to create a specification for your new feature using the spec-driven-development workflow before writing any code.
