speckit-analyze

To check for inconsistencies between spec, plan, and tasks files, run a read-only analysis that compares spec.md, plan.md, and tasks.md to detect contradictions, duplications, ambiguities, and coverage gaps before implementation begins.

A constitution validation check reviews your project artifacts against .specify/memory/constitution.md, flagging any conflicts with MUST principles as CRITICAL severity findings to ensure mandatory requirements are enforced before development starts.

You find coverage gaps and missing acceptance criteria by cross-referencing your spec, plan, and tasks together, which flags vague success criteria, placeholders, and tasks lacking mapped requirements for you to fix.

You should run a specification analysis immediately after tasks.md generation occurs in your speckit project, ensuring all artifacts are complete and ready to be cross-referenced for inconsistencies before moving into implementation.

No, the spec-plan-tasks analysis runs strictly in read-only mode to audit your files, ensuring your original specifications, plans, and tasks remain unmodified while producing a token-efficient Markdown report of severity-ranked findings.