Claude SDD
Spec-Driven Development. Stop prompting. Start specifying. Write clear specs with acceptance criteria, then let Claude Code implement them with TDD, quality gates, and specialized agents.
Why Spec-Driven Development?
Specs Before Code
Define what you're building before how. Feature specs with acceptance criteria become the contract between you and AI. No more vague prompts or misunderstood requirements.
Living Documentation
Specs evolve as you learn. Unlike static PRDs, your SPEC.md files adapt during implementation. Discoveries get captured, requirements get refined.
Test-First Implementation
Every task follows TDD: write failing tests (RED), implement until they pass (GREEN), then refactor. Quality gates enforce review scores before moving on.
Acceptance-Driven Completion
Tasks aren't done when code compiles. They're done when acceptance criteria from the spec are met, tests pass, and the code review clears.
Architecture Decision Records
Technical decisions get documented in ADRs before implementation. "What database?" becomes a reasoned decision with context, not a hasty choice.
Full Traceability
Spec → Task → Plan → Implementation → WORKLOG. Every decision, every phase, every commit traced back to requirements. No more "why did we build this?"
The Spec-Driven Workflow
# 1. Define your project vision /project-brief # 2. Write a feature spec with acceptance criteria /spec # 3. Create tasks from the spec /issue "implement user login from SPEC-001" # 4. Plan TDD phases for the task /plan 001 # 5. Implement with specialized agents /implement 001 --full # 6. Verify acceptance criteria met /complete 001
Get Started in Seconds
Install the plugin and initialize your project with spec-driven templates