What problem does it solve? Code written without a specification is guessing. This Skill prevents rework by forcing requirements, assumptions, and success criteria into a written, human-approved spec before any implementation begins. ## Core Features & Use Cases - Gated Four-Phase Workflow: Moves through Specify, Plan, Tasks, and Implement phases, each requiring human review before advancing. - Capability Decomposition: Detects when one request bundles several independently testable capabilities and proposes a capability map with module ids, dependencies, and build order before any spec is written. - Spec Template with Boundaries: Produces specs covering objective, commands, project structure, code style, testing strategy, and Always/Ask First/Never boundaries. - Use Case: When asked to build a new billing feature with vague requirements, use this Skill to surface assumptions, reframe "make it faster" into measurable success criteria, and produce an approved spec before touching code. ## Quick Start Use the spec-driven-development skill to write a specification for the new notification feature before implementing it.
