spec-driven

Spec-driven development coordinates requirements, design, tasks, and implementation through sequential phases with approval gates. Launch the requirements-agent to start, then transition through design and task phases with user feedback between each stage, ensuring structured planning before code implementation.

Spec-driven development enforces a phased workflow: Phase 1 gathers requirements, Phase 2 designs solutions, Phase 3 breaks work into tasks, and Phase 4 optionally implements—each with mandatory approvals. This prevents rework by validating assumptions early rather than discovering misalignment during development.

The orchestrator manages transitions between phases by waiting for subagent completion, collecting user feedback at each gate, and gating the next phase on approval. This ensures stakeholders validate requirements before design, design before task breakdown, and tasks before implementation begins.

Yes. The workflow covers Phase 1 requirements, Phase 2 design, and Phase 3 task breakdown as mandatory stages, with Phase 4 implementation optional. You can complete structured planning, get approval, and defer coding until later.

The orchestrator forbids direct document creation to enforce subagent specialization—each agent brings focused expertise to its phase. Delegating to specialized subagents produces higher-quality requirements, design, and tasks than a single handler writing all outputs.

The orchestrator launches automatically when you request structured feature planning or explicitly say 'use spec-driven'. Either trigger initiates the full workflow, starting with requirements gathering through the requirements-agent.