speckit-analyze

To check consistency between project specifications and task lists, run a cross-artifact validation that evaluates alignment across spec.md, plan.md, and tasks.md to identify coverage gaps and ambiguities.

Project specification drift is the misalignment between high-level requirements, implementation plans, and task lists. You prevent it by performing a non-destructive quality analysis to detect inconsistencies and duplications before coding begins.

Yes, you can validate functional requirements against a project constitution automatically. The analysis enforces compliance by checking all project artifacts against established normative principles and core architectural constraints.

Yes, you need a valid spec-kit project structure to analyze task coverage. The validation process requires this specific structure to verify that every success criterion is covered by a task and adheres to normative principles.

The best way to verify every success criterion is covered by a task is to run a cross-artifact validation after generating your task list. This detects ambiguities and validates alignment between functional requirements and granular tasks.