speckit-analyze

To check spec consistency post-task generation, analyze your project specifications and tasks to identify inconsistencies, duplications, and ambiguities. This process inspects spec, plan, and tasks documents to ensure proper implementation without modifying files.

Spec-kit project structure requires a .specify/ directory to validate project specifications. You need it when running project-specific hooks and checking constitution compliance to ensure proper specification analysis.

No, specification analysis does not modify your project files during consistency checks. It produces a structured analysis report that identifies errors, conflicts, and underspecified items while keeping your spec, plan, and tasks documents intact.

Yes, you can target specific focus areas when analyzing project specifications. Optional focus areas allow targeted review of your spec, plan, and tasks documents, enabling you to concentrate the consistency and quality analysis on particular sections.

The best way to prevent implementation errors from inconsistent project specifications is to perform a post-task generation consistency and quality analysis. This identifies duplications, ambiguities, and conflicts across your spec, plan, and tasks documents before coding begins.

Specification analysis may fail when checking constitution compliance if your project lacks the required spec-kit structure. Ensure your project includes a .specify/ directory, as the analysis relies on project-specific hooks to validate compliance.