speckit-analyze

To check inconsistencies across spec, plan, and tasks before coding, analyze cross-artifact gaps between spec.md, plan.md, and tasks.md. This process identifies duplications, ambiguities, and underspecified items to prevent implementation defects.

You should run cross-artifact consistency analysis after task generation is complete and before implementation begins. It validates the spec.md, plan.md, and tasks.md artifacts against constitution principles to ensure alignment prior to development.

The best way to identify gaps between spec.md and tasks.md is to perform a cross-artifact consistency analysis. This flags overlaps and underspecified items across the documents, outputting a structured analysis report to highlight missing requirements.

Yes, you can automatically generate an optional remediation plan for missing spec requirements. The analysis identifies gaps across your artifacts and provides targeted remediation guidance to resolve inconsistencies before implementation starts.

Yes, cross-artifact analysis validates project documents against constitution principles. While detecting gaps and overlaps across spec.md, plan.md, and tasks.md, it ensures the artifacts align with established project rules before implementation proceeds.