Agent skill · magnus919
spec-driven-development
Spec-Driven Development (SDD) methodology for AI software factories —
What it needs
About 8k tokens when loaded.
What this skill does
Spec-Driven Development for AI Software Factories A methodology for building software where specifications are the executable input to an AI code generation pipeline. The factory model: specs are blueprints, AI agents are the assembly line, verification is quality control, and gates catch defects before they compound. Pipeline Overview Each phase passes through a gate before the next begins. A defect caught at Gate 1 costs minutes to fix; the same defect found at Gate 4 costs hours. SDD Core Principles 1. Precision over clarity. A precise-but-dense spec is better than a readable-but-ambiguous one. The AI cannot ask for clarification — it implements one interpretation at random. 2. Completeness over brevity. Every missing acceptance criterion is a missing feature. Specifying an edge case upfront costs minutes; discovering it in production costs hours or days. 3. Testability over descriptiveness. An AC that cannot produce CLEAR PASS or CLEAR FAIL is not an AC — it's a hope. 4. Gates catch defects early. A Gate 1 (spec review) fix costs minutes. A Gate 4 (acceptance review) fix costs hours — the entire implementation may need to be discarded. 5. Spec is the single source of truth. Every downstream artifact traces back to the spec. Deviations are defects unless explicitly documented. 6. Spec IS the test (when possible). Gherkin-style ACs serve double duty as test cases. No separate test writing required. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills magnus919/spec-driven-development