spec-driven-developmentlisted

# Spec-Driven Development ## Overview SDD makes **specifications the source of truth** — code serves specs, not the other way around. Instead of prompting an AI with vague descriptions and hoping for the right output, you define precise specifications first, then let AI generate code strictly constrained by them. Without a spec, AI makes thousands of micro-decisions silently. With a spec, those decisions are made by you — explicitly, before any code is written, which is what turns a pivot into a systematic regeneration rather than a manual rewrite. ## Quick Start 1. `/sdd:init` — create `constitution.md` (once per project, before any feature spec) 2. `/sdd:research [description]` — map how the existing code works, cited `file:line` (skip on greenfield) 3. Surface and correct the AI's implicit assumptions *before* any AC is written 4. `/sdd:specify [description]` — generate `spec.md` with MoSCoW-prioritized ACs 5. Follow the gates: Clarify → Plan → Tasks → Implement → Validate, with human approval at each Step-by-step detail: `references/workflow-phases.md`. ## When to Use Symptoms that signal SDD is needed: - AI ignores constraints or generates code that doesn't match requirements - Same prompt produces different implementations across sessions - Requirements are complex with multiple stakeholders or cross-cutting concerns - Team needs shared technical understanding before writing code - Feature touches auth, data model, API contracts, or database schema **Skip enti