Spec-Driven Development has an agent write a specification first and treat it as the shared source of truth with the human engineer. A gated workflow moves through specify, plan, tasks and implement, and the agent stops after saving the spec so the human can approve it in a later turn.
The spec template covers objective, commands, project structure, code style, testing strategy and boundaries. An optional scope check builds a capability map for requests that bundle several independent capabilities, and later changes get a delta spec.
What You Get
- A gated four-phase workflow with an optional scope check
- A spec template with six core areas
- A capability map template and a delta spec template
- Rules for keeping the spec current, red flags and a verification checklist
Common Use Cases
- Starting a new project or feature
- Clarifying vague requirements into success criteria
- Decomposing a large request into modules
- Scoping V1 and deferring ideas to V2
What Makes It Unique
The skill ends the agent’s turn once the spec is saved so planning cannot start without approval. It handles scope growth through an Out of Scope list, a capability map for bundled requests and delta specs for shipped features.
Under The Hood
The skill is a single SKILL.md of instructions. It runs no scripts. The agent writes spec files in the repository, such as spec/capability-map.md and module specs, and hands off to the planning, incremental implementation, test-driven and context engineering skills in later phases.