What problem does it solve?
Identify inconsistencies, ambiguities, duplications, and coverage gaps across spec.md, plan.md, and tasks.md before implementation so teams catch blocking issues and constitution violations early in the workflow. The analysis is strictly read-only and prioritizes constitution MUSTs, measurable success criteria, and task coverage for requirements.
Core Features & Use Cases
- Read-only cross-artifact analysis: Parses spec, plan, and tasks to map requirements, user stories, and tasks without modifying repository files.
- Constitution validation: Loads the project constitution to surface any direct conflicts as CRITICAL issues.
- Compact, actionable report: Produces a severity-labeled Markdown findings table, coverage summary, unmapped tasks list, and concise next actions for remediation.
- Use Case: Run after speckit.tasks produces tasks.md to verify that every functional requirement and buildable success criterion has task coverage and that terminology and file references are consistent.
Quick Start
Run speckit-analyze on the feature directory to produce a compact Markdown analysis of spec.md, plan.md, and tasks.md.