spec-driven-dev

Spec-Driven Development

Specs live in .kiro/specs/<NN-name>/. Numeric prefixes for ordering (01-auth, 02-api-layer). Two modes:

• Full ceremony (requirements.md → design.md → tasks.md): formal traceability, approval gates, multi-team
• Fast-track (single spec.md): one scratchpad for planner/builder/reviewer — no gates, cycle freely between hats

Detection: spec.md → fast-track. requirements.md → full ceremony. Never mix both. Small work: Add to an existing spec as tasks, or create a fast-track spec. Upgrade: Fast-track → full when >20 tasks or traceability needed: Context → requirements.md, Decisions → design.md, Tasks → tasks.md.

Spec Lifecycle

Every spec has a status. Write it in the first line of the top-level spec file (spec.md or requirements.md) as Status: <STATE> (plus a Since: date).