speckit-analyze

To check spec-plan-task consistency, run an analysis from the repository root after generating tasks.md. This surfaces inconsistencies, duplications, ambiguities, and under-specified items across the three core artifacts.

Traceability mapping relates each requirement and task to its originating narrative, checking coverage to ensure every item is tracked. It maintains links between spec.md, plan.md, and tasks.md artifacts.

To validate spec-kit constitution principles, run an analysis that detects violations of MUST and SHOULD principles. It ensures mandatory sections exist within spec.md, plan.md, and tasks.md artifacts.

Run a preflight check on spec, plan, and tasks files before implementation to identify undefined references and missing sections. This prevents gaps and redundancies from carrying into development.

Vague requirements and duplications are flagged across spec, plan, and tasks to surface conflicts and gaps. Identifying under-specified items ensures alignment across the three core artifacts before implementation.