speckit-analyze

To check software specification documents for consistency, you can analyze spec.md, plan.md, and tasks.md files to detect inconsistencies, duplications, and ambiguities. This ensures specification quality and reduces post-implementation risks.

Specification analysis is the process of reviewing project documents to find ambiguities, duplications, and underspecification. It performs non-destructive checks on your specification artifacts and outputs a detailed analysis report identifying potential quality issues.

Yes, you need a spec-kit project structure to run consistency checks on your specifications. The analysis tool requires this specific project layout to read and validate your spec.md, plan.md, and tasks.md documents effectively.

You can validate specification compliance against a project constitution automatically by running a specification analysis. It checks your documents for adherence to defined standards and principles, ensuring your specifications meet required quality benchmarks.

Specification analysis does not modify your task and plan documents during the quality check. It operates with a strict read-only constraint, preserving your original artifacts while generating a detailed report of detected inconsistencies and ambiguities.

You should run a specification consistency check before committing work units in your software development workflow. This verifies that your spec, plan, and task documents meet quality standards and identify underspecification before implementation begins.