speckit-analyze

To check consistency between project artifacts, you can run a non-destructive quality analysis that evaluates requirements coverage and detects ambiguity across spec.md, plan.md, and tasks.md. This process flags inconsistencies, duplications, and coverage gaps automatically.

Cross-artifact validation is the process of detecting inconsistencies, duplications, and coverage gaps between spec.md, plan.md, and tasks.md. It ensures that every success criterion is covered by a task and aligns with architectural constraints.

Yes, validating spec.md and tasks.md alignment requires a valid spec-kit project structure containing a .specify directory. This directory is necessary to execute prerequisite checks and parse project artifacts during the consistency analysis.

To enforce project constitution principles during task generation, perform a consistency analysis that flags technical or functional requirements violating defined memory and constitution principles. This validates alignment against your architectural constraints.

You should run a requirements coverage analysis after generating a complex task list for a new feature. This verifies that every success criterion is covered by a task and ensures your development work remains strictly aligned with project specifications.

Yes, consistency analysis detects ambiguity in implementation plans by evaluating requirements coverage across spec.md, plan.md, and tasks.md. The non-destructive evaluation identifies gaps and validates alignment to eliminate drift between artifacts.