spec-driven-development

To keep code and specifications synchronized, align implementation with formal specs located in .claude/specs/ and enforce alignment checks during development. This prevents drift by updating specs or code when divergence is discovered, maintaining a single source of truth.

Spec-driven development is a workflow that prevents drift between implementation and formal specs by keeping both sources synchronized and auditable. Use it during feature kickoff, ongoing implementation, and verification tasks when formal specifications exist in .claude/specs/.

Verify code alignment with formal specifications by running spec verification tasks that check implementation against the authoritative specs in .claude/specs/. The process records verification results to ensure traceable alignment across code and documentation.

Yes, you need existing formal specifications in .claude/specs/ to use spec-driven development. The workflow drives implementation from these authoritative specs and enforces alignment checks against them during development and verification tasks.

Handle divergence between specs and implementation by updating specs or code when divergence is discovered. This maintains a single source of truth and ensures traceable alignment across both sources during the development workflow.

Spec drift happens when implementation changes without corresponding spec updates, breaking synchronization. Spec-driven development prevents this by enforcing alignment checks during development and updating specs or code when divergence is discovered in .claude/specs/.