spec-driven-devlisted

## Spec-Driven Development Specs live under `<SPECS_ROOT>/<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. ### SPECS_ROOT resolution Different projects use different conventions. Resolve once at entry, never hard-code a path. Resolution order (first match wins): 1. `specs_root:` line in `CLAUDE.md` or `AGENTS.md` at the repo root. 2. `.kiro/specs/` if it exists. 3. `specs/` at the repo root if it exists. 4. Brand-new project with neither: default to `.kiro/specs/`. Sibling artifacts live alongside the chosen specs directory: | Specs root | Ledger | Steering docs | |----------------------|--------------------------|----------------------| | `.kiro/specs/` | `.kiro/FEATURES.md` | `.kiro/steering/` | | `specs/` (repo root) | `FEATURES.md` (repo root)| `steering/` (repo root)| Throughout this skill, **SPECS_ROOT** is the resolved specs directory and **LEDGER** is