spec-driven-workflow

Use when creating, updating, reviewing, implementing, or closing software Specs and linked task documents, including re-scoping tasks that become difficult to verify during execution, tracking confirmed follow-up implementation in a repository TODO index, and archiving completed task documents without losing historical traceability. Also use for non-trivial changes, refactors, or migrations that need stable acceptance criteria, bounded deliverables, verification evidence, consistency review, and document lifecycle handling. Do not use for general documentation, simple questions, routine low-risk edits, one-line changes, or explicitly plan-free work.