Spec Driven Development

Keeps your specs and code from drifting apart by enforcing a tight loop: read the spec in .claude/specs/, implement, verify alignment, update whichever side changed. It'll check off TODOs as you go, flag when you diverge from architectural decisions, and run verification passes to catch drift in API contracts, config values, or module structure. Useful on any project where you're tired of docs rotting the moment implementation starts. The discipline feels heavy at first but pays off when you're three weeks in and the spec still matches reality. Works best when specs are concise and treated as living documents, not write once artifacts.