speckit.analyze

To find inconsistencies, perform cross-artifact analysis across spec.md, plan.md, and tasks.md files. This surfaces duplications, ambiguities, and underspecified items, generating a structured report with alignment recommendations to reduce rework.

Cross-artifact validation checks for conflicts and coverage gaps across specification, planning, and task documents. It enforces project constitution alignment to ensure all SDLC artifacts are consistent before implementation begins.

Yes, you need a completed tasks.md file to analyze consistency. The analysis relies on the tasks.md artifact produced by speckit.tasks to accurately identify gaps and conflicts against your spec.md and plan.md documents.

To get remediation guidance for ambiguities, run an analysis across your spec, plan, and task files. It generates a structured report offering optional, reviewable steps to align artifacts and resolve underspecified items before committing edits.

The best way to enforce constitution alignment is to analyze your spec.md, plan.md, and tasks.md files together. This cross-artifact validation identifies inconsistencies and ensures all planning and task documents adhere to project standards.

Your spec analysis report shows underspecified items because cross-artifact validation detected missing details or coverage gaps between your tasks.md and the corresponding spec.md and plan.md documents before implementation.