cc-sdd — Spec-Driven Implementation Skills for Agents

Practical Notes

• Quant: the README calls out 17 skills across 8 agents and 13 languages—start with 1 agent + 1 language in production, then expand.
• Quant: measure cycle time per phase (discovery→requirements→design→tasks→impl) on 3 similar features before and after adoption.

Make specs a contract, not a monolith

Spec-driven delivery works when you treat outputs as contracts:

• Requirements define acceptance criteria.
• Design defines boundaries.
• Tasks define interfaces and dependencies.

A rollout recipe

1. Pick one feature that is “medium sized”.
2. Run discovery, then stop and review brief.md / roadmap.md.
3. Only then run the implementation flow.

Guardrails that matter

• Keep feature flags for autonomous changes.
• Require an independent review pass.
• Use a failure log: every agent failure must become a checklist item or test.

FAQ

Q: Will this slow down small changes? A: Use it selectively: spec-driven shines on medium/large work; tiny fixes can skip full phases.

Q: What is the biggest win? A: Less context thrash: phases are explicit and artifacts are resumable.

Q: How do I keep quality high? A: Gate each phase: humans approve the contract before the next phase runs.