speckit-analyze

To check spec, plan, and task files for inconsistencies, run a cross-artifact analysis that identifies duplications, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md. This validates requirements mapping and constitution alignment to prevent implementation churn.

Cross-artifact consistency analysis in software specification is a read-only review process that maps requirements and success criteria to task coverage. It detects inconsistencies, duplications, and ambiguities across spec.md, plan.md, and tasks.md to validate alignment against non-negotiable constitution principles.

You need to run specification and task coverage analysis immediately after generating tasks.md. It performs dependency-aware execution that requires a complete tasks.md file to successfully map requirements and identify coverage gaps before you begin building.

No, spec-plan-task analysis does not modify your specification files during review. It performs non-destructive cross-artifact analysis to identify inconsistencies, outputting a compact Markdown report capped to 50 findings that details coverage gaps and next actions.

Limitations of automated requirements mapping and consistency analysis include a hard cap of 50 findings per detection pass and strict dependency prerequisites. It requires successful task generation and prerequisite discovery via check-prerequisites.sh before loading minimal context to produce its structured report.