Spec-Driven Development (SDD)

Spec‑driven development means writing an explicit, implementation‑agnostic specification first (the what/why and acceptance criteria), then deriving a technical plan and tasks from it before generating or writing code. This reduces ambiguity, improves repeatability, and helps avoid “vibe coding.”

• TODO: Expand this note with a fuller description, examples, and a lightweight template (spec → plan → tasks), plus pros/cons.

References

• The ONLY guide you’ll need for GitHub Spec Kit
• AI-assisted Coding Workflows
• Beyond Vibe Coding with Addy Osmani
• Kiro
• Vibe coding workflow for non-technical people using Cursor and AI
• PRDs and Design Docs
• Four Modes of AI-Assisted Coding

Seed Ideas / Prompts

• Treat the spec as the single source of truth; regenerate plans or code against it as needed.
• Keep specs implementation‑agnostic; attach acceptance criteria and open questions.
• Use scripts for deterministic steps; let LLMs draft plans/code under review.