speckit-analyze

You can check consistency across spec, plan, and tasks files by running a post-task generation analysis. This process evaluates the documents for duplication, ambiguity, underspecification, and coverage gaps, providing a detailed report without modifying the source files.

Constitution alignment in project analysis verifies that your generated tasks and plans adhere to the foundational project constraints. This consistency check ensures the core artifacts remain consistent with the established constitution before implementation begins.

To detect coverage gaps in a spec-kit project, you perform cross-artifact analysis between spec.md, plan.md, and tasks.md. This quality analysis identifies missing requirements and ensures all specifications are fully covered by the generated tasks.

Yes, you need a spec-kit project structure containing a .specify/ directory and specific artifacts to analyze. The consistency and quality analysis also requires the .specify/extensions.yml file to configure additional hooks for checking duplication and coverage gaps.

Yes, you can run a non-destructive consistency check that analyzes your spec, plan, and tasks without modifying the source files. It performs read-only cross-artifact checks and outputs a detailed report of identified issues and recommendations.

You should run a quality analysis on your project artifacts post-task generation, right before implementation begins. This timing allows you to identify and resolve consistency issues, ambiguity, and underspecification early in the development lifecycle.