Section 7
Advanced SDD Use Cases
Apply SDD beyond the basics — evidence-driven debugging, spec-first modernization, and compiling one spec to many targets.
"Compiling is the beginning. Done is conformance.
3 lessons · ~42 min
Lessons
Lesson 1
Lesson 1 · Evidence, not guesswork
Spec-First Debugging
Treat the spec as the case file — MCP detective, Playwright reenactment, DevTools forensics, six-step runbook, LCP and jank case studies, spec feedback loop.
Lesson 3
Lesson 3 · Recover intent, then replace
Legacy Modernization
Intent decay, the modernization trap, characterization tests, spec.md, the Strangler Fig Pattern, AI-assisted rebuilds, and done as conformance — not compile.
Lesson 4
Lesson 4 · One spec, many targets
Compile the Product
Treat divergence as a compiler problem: spec as IR, Go and Rust as backends, frozen contracts, functional vs aesthetic UI, Figma as design truth, engineered determinism.
Practical takeaways
- 1Lesson 1: Debug from the spec first — measurable journeys, budgets, and acceptance criteria before touching code.
- 2Lesson 3: Do not rewrite the how until you have recovered the why — intent decay is the real villain.
- 3Lesson 4: Stop patching twin codebases. Compile one spec to many targets.
- 4Functional, contract, and quality invariants cannot change between variants — only the how can.
- 5Determinism is engineered: versioned spec, pinned dependencies, repeatable pipelines, traceable artifacts.