What problem does it solve? Specification-driven development produces multiple artifacts (spec, plan, tasks) that can drift apart, leaving duplicated requirements, ambiguous wording, uncovered requirements, and conflicts with project principles that only surface during implementation. ## Core Features & Use Cases - Cross-Artifact Consistency Analysis: Detects duplications, ambiguities, underspecification, terminology drift, and conflicting requirements across spec.md, plan.md, and tasks.md. - Coverage Mapping: Builds a requirement-to-task coverage map and reports requirements with zero tasks and tasks with no mapped requirement. - Constitution Enforcement: Validates artifacts against the project constitution, treating MUST-principle violations as CRITICAL findings. - Use Case: After running /speckit.tasks to generate tasks.md, run this analysis to receive a severity-ranked report with a coverage summary and metrics before starting implementation. ## Quick Start Run the speckit analyze command to check my spec, plan, and tasks files for inconsistencies and coverage gaps before implementation.
