Spec Driven Development

How to build a CI gate that fails when a coding agent changes spec-tagged test assertions or spec example outputs without changing the spec clause they cite, plus the structured waivers and agent-readable errors that stop the team from clicking past it.

How to write the constitution, spec, plan, and tasks so each decision sits on the right artifact and an agent builds only what you asked.

You'll learn why an agent's plan silently loses spec constraints like transaction boundaries and idempotency, and how to catch those gaps with a traceability check before they reach production.

How to triage a spec an AI recovers from a legacy system — deciding which behaviors to keep, kill, or preserve — before you forward-build the replacement.

How to use SDD to reverse-derive a tested, executable spec from a legacy system you're afraid to touch, and why that spec matters more than any rewrite.

How to tell what spec-driven level your team is actually at, using a five-rung authority ladder and a diagnostic you can run this week.

You'll learn why, once an agent can regenerate code from a spec, the spec becomes the source of truth and the code becomes disposable build output — and how that changes hand-fixes and PR review.

A single verb — 'remove' — sat quietly in a ticket for weeks until an agent picked its own meaning, and by the time anyone noticed, the fix wasn't a wording tweak but a whole new way of writing specs.