speckit-analyze

Requirements traceability and consistency checking for spec.md, plan.md, and tasks.md is a cross-artifact analysis that detects duplications, terminology drift, ordering conflicts, and mismatches before implementation starts.

To check task coverage and constitution alignment, run a read-only analysis after task generation to validate requirement mappings, flag missing coverage, and report any MUST/SHOULD principle violations as critical issues.

To detect ambiguity and underspecified requirements in speckit artifacts, perform a read-only analysis that flags vague success criteria, unresolved placeholders, and requirements lacking measurable outcomes or object definitions.

speckit-analyze does not modify your spec.md, plan.md, or tasks.md files during validation. It satisfies read-only reporting constraints by loading artifacts and the constitution to output a compact Markdown analysis report with severity-ranked findings.

You should run cross-artifact consistency analysis on your speckit project immediately after tasks.md generation finishes, ensuring you find contradictions, duplication, and missing coverage before engineering cycles begin.

The best way to validate constitution alignment and task coverage in a .specify directory structure is to load the artifacts and constitution, build semantic inventories and mappings, and generate a severity-ranked Markdown report of inconsistencies.