spec-driven-development

# Spec-Driven Development Use this workflow for non-trivial features and behavior-changing fixes. The user-started primary conversation performs every phase by default. Plans may describe parallel work, but subagents are used only when the user explicitly authorizes them after selecting the implementation model. ## Core Flow ```text Intent -> Spec -> Plan + task files -> User model switch -> Sequential TDD implementation -> PR AI review -> Report ``` Do not replace the spec, plan, or task files with chat-only notes. Do not skip from intent to code unless the user explicitly opts out of this workflow. ## Phase 0: Track The Work Keep a visible task list and mark each phase as it completes: 1. Clarify intent 2. Create or update the spec 3. Create the implementation plan 4. Decompose it into task files 5. Pause for the user to switch the main model 6. Execute tasks with TDD and targeted checks (sequential by default) 7. Open PR, address CI/review findings, record, and summarize ## Phases 1–4: Design On The Strong Model Use `/interview-me` only when the request is underspecified. Create or update: - `docs/specs/<slug>/spec.md` through `/spec` for the durable product behavior. - `docs/plans/<slug>/plan.md` through `/plan` for the technical sequence. - `docs/plans/<slug>/task-<NN>-<short-slug>.md` for each independently actionable implementation step. The spec must cover relevant scenarios, contracts, permissions, failures, and persistence guarantees. The plan must name...