speckit-analyze

Cross-artifact consistency analysis checks your spec.md, plan.md, and tasks.md to surface gaps, duplications, and ambiguities before implementation begins. It ensures requirements coverage and alignment with project principles to prevent downstream errors.

Cross-artifact gap analysis is the process of identifying ontology drift and conflicting terminology across your specification, planning, and task documents. It enforces structured analysis of requirements and constitutional rules to surface actionable remediation items.

You need to analyze gaps after your tasks.md is complete and before implementation begins. Running this analysis at the post-planning stage ensures your tasks align with the spec and plan, verifying readiness for downstream development work.

Detecting duplications and conflicting terminology requires comparing your spec, plan, and tasks files for overlapping definitions and ontology drift. A structured cross-artifact analysis identifies these ambiguities and generates a remediation-ready coverage report.

Yes, analyzing cross-artifact consistency generates a remediation-ready coverage report aligned to your project principles. This report highlights detected gaps, duplications, and ambiguities across your artifacts to guide necessary corrections.

Cross-artifact consistency analysis relies on a complete tasks.md produced by the prior planning stage. It cannot surface gaps effectively if your spec, plan, or tasks documents are incomplete or missing foundational requirements.