speckit-analyze

Cross-artifact consistency is checked by automating the identification of inconsistencies and quality gaps across spec.md, plan.md, and tasks.md. This validation ensures alignment between functional requirements, user stories, and tasks, producing a structured analysis report with remediation suggestions.

Cross-artifact validation is the process of verifying alignment and consistent terminology between functional requirements, user stories, and tasks. It surfaces inconsistencies and quality gaps across spec.md, plan.md, and tasks.md before implementation begins.

Validating against a constitution verifies adherence to project principles and governance defined in .specify/memory/constitution.md. The analysis checks the artifacts for alignment with these established rules and reports any deviations.

Yes, you need to run /speckit.tasks to produce tasks.md before analysis. The consistency analysis applies to speckit-based projects where tasks.md has been generated and a constitution is defined in .specify/memory/constitution.md.

No, the validation is non-destructive and produces a read-only analysis report. It does not modify any source artifacts, ensuring your original spec.md, plan.md, and tasks.md files remain untouched while providing optional remediation suggestions.

The best way to surface inconsistencies is to run a non-destructive cross-artifact analysis that checks alignment between functional requirements, user stories, and tasks. This generates a structured report highlighting issues and suggested remediation steps.