speckit-analyze

To check for inconsistencies between spec, plan, and tasks files, run a cross-artifact analysis comparing spec.md, plan.md, and tasks.md to detect duplications, ambiguities, and underspecifications, generating a structured report without modifying files.

Spec analysis is the process of verifying logical coherence across project artifacts. It detects requirement gaps by flagging functional requirements in spec.md that lack corresponding implementation tasks in tasks.md, ensuring complete project coverage.

Yes, you can verify constitution adherence by analyzing project artifacts against defined project principles. The analysis ensures no task contradicts the constitution, confirming alignment and preventing principle violations before development begins.

You do not strictly need a constitution file to perform a consistency check on project artifacts. The analysis primarily requires spec.md, plan.md, and tasks.md to detect duplications and gaps, while constitution alignment is an additional verification layer.

The best way to find tasks without corresponding requirements in project planning is to perform a cross-artifact gap detection analysis. This flags tasks in tasks.md that lack backing requirements in spec.md, identifying underspecifications and scope creep.

No, the spec analysis will not automatically modify your project files to fix ambiguities. It generates a structured report offering remediation suggestions for duplications and ambiguities, leaving all artifact files unchanged for manual review.