analysis-phase

Cross-artifact consistency validation works by analyzing spec.md, plan.md, and tasks.md to verify spec-to-plan mappings and plan-to-task coverage. The process checks alignment across these files to surface actionable findings before deployment.

Breaking change detection flags API, database, UI, and auth changes during feature analysis. By cross-checking artifacts during the analyze phase, it identifies potential integration risks early to enable reliable delivery and risk mitigation.

Dependency validation cross-checks imports and external integrations referenced in plan and tasks files. It analyzes these dependencies alongside spec-plan alignment to ensure referenced components are consistent across all project artifacts.

To generate an analysis report, run an analysis against your current specs directory to produce an analysis-report.md file. The process validates spec-plan-tasks consistency and updates state.yaml with the resulting analysis findings.

Cross-artifact consistency validation is needed during the analyze phase before deployment. It should be run when you have spec.md, plan.md, and tasks.md files that require alignment verification to detect breaking changes and dependency issues early.

Consistency validation requires no external dependencies or components to operate. It functions as a standalone analysis tool that reads your existing spec.md, plan.md, and tasks.md files to generate reports and update state.yaml.