speckit-analyze

To check for inconsistencies across spec, plan, and tasks files, run an analysis command that loads minimal context from each artifact and enforces constitution rules to surface duplications, ambiguities, and gaps. It generates a findings report with coverage metrics for review.

Ambiguities and underspecified items after task generation occur when spec.md, plan.md, and tasks.md fall out of alignment. Analyzing these artifacts cross-references their content to detect gaps and enforce constitution rules, providing remediation hints to resolve the issues.

To detect duplicated or underspecified tasks before implementation, perform a cross-artifact consistency check across your spec, plan, and tasks documents. This process identifies duplications and gaps, outputting a compact findings report and an optional remediation plan.

No, spec and plan artifact review does not require loading the full project context. The analysis loads only minimal context from each artifact to enforce constitution rules and surface critical issues, ensuring efficient quality assurance before implementation begins.

You need cross-artifact consistency checks for project governance after task generation and before implementation. This analysis enforces constitution alignment by identifying inconsistencies, duplications, and ambiguities across spec.md, plan.md, and tasks.md.

The report from analyzing spec, plan, and tasks includes a compact findings report detailing inconsistencies and ambiguities, coverage metrics, and an optional remediation plan. These outputs guide review sessions and ensure constitution alignment.