speckit-analyze

To check for coverage gaps, you need a cross-artifact review that maps requirements to tasks and flags unmapped items. This process compares spec.md, plan.md, and tasks.md to surface missing success criteria and implementation drift.

You need a spec review after task generation and before implementation starts. Analyzing artifacts at this stage catches duplication, ambiguity, and conflicts early, ensuring the implementation work is fully ready and aligned with requirements.

Yes, you can validate constitution alignment by checking spec, plan, and tasks against required project principles. This flags any mismatches with quality gates and ensures the generated tasks adhere to foundational project constraints.

No, this spec review process is strictly read-only. It analyzes the artifacts to report prioritized findings and coverage metrics without modifying your spec.md, plan.md, or tasks.md files.

The best way to find unmapped requirements is to perform cross-artifact coverage analysis. This maps your specification requirements directly to tasks and flags any items that lack corresponding implementation work.

Tasks drift from specifications due to inconsistencies, ambiguity, or missing coverage during generation. A cross-artifact review identifies these conflicts and reports prioritized findings to realign the tasks with the spec.