speckit-analyze

To check spec, plan, and task files for inconsistencies, you need a cross-artifact consistency checker that identifies duplications, vague requirements, and missing mappings across spec.md, plan.md, and tasks.md before implementation begins.

Requirements traceability analysis in a spec-kit workflow validates that generated tasks.md aligns with constitution-aligned requirements, detecting coverage gaps and underspecified items across project artifacts to prevent broken implementations.

To validate generated tasks against constitution principles, you enforce read-only analysis using .specify/memory/constitution.md as a non-negotiable authority, checking extension hooks and outputting structured findings with coverage metrics.

You should run consistency checking on specification documents immediately after /speckit-tasks generates a complete tasks.md, ensuring cross-artifact alignment and resolving ambiguities before you start building the project.

Spec-kit analysis requires .specify/memory/constitution.md as a non-negotiable authority to enforce constitution principle alignment, meaning the file is necessary to validate constitution-aligned requirements and output structured findings.

Your tasks.md has coverage gaps after generation due to missing mappings between spec.md and plan.md, which cross-artifact consistency checking identifies by detecting duplications, ambiguities, and underspecified items across the three core artifacts.