What problem does it solve?
Coordinating the lifecycle of a spec-driven effort is complex: it requires SPIDR-splitting, state transitions, and governance gates across slices, docs, and ADRs. This skill provides a deterministic framework to manage that lifecycle, drive decisions, and surface drift or stale content.
Core Features & Use Cases
- SPIDR-splitting of non-trivial specs into vertical slices for end-to-end value delivery.
- Deterministic state transitions (DRAFT → READY_FOR_REVIEW → READY_FOR_IMPLEMENTATION → IN_PROGRESS → REVIEWED → RECONCILED → DONE; with DEFERRED parking) and reconciliation gating.
- Observability and governance surfaces (routing stats, project coverage, and traceability through use_cases and memory glossary) to prevent drift and ensure consistent delivery.
Quick Start
Use the spec-workflow tool to SPIDR-split a spec and begin tracking its lifecycle from draft to done.