analysis-phase

Cross-artifact consistency validation analyzes spec.md, plan.md, and tasks.md to identify gaps and orphaned artifacts. It enforces dependency validation and constitution-based risk checks to catch inconsistencies before deployment.

Breaking-change detection identifies risky modifications across spec, plan, and task artifacts during feature analysis. It applies constitution-based risk checks and generates an analysis-report.md to prevent deployment issues.

Automated cross-artifact validation detects spec-plan-task gaps and orphaned artifacts by enforcing dependency and consistency checks. It outputs an analysis-report.md with a state update to ensure deployment readiness.

Yes, cross-artifact validation runs without external dependencies. It performs constitution-based risk checks and breaking-change detection across specs, plans, and tasks to generate an analysis-report.md independently.

Execute an analysis workflow to validate cross-artifact consistency, detect breaking changes, and check dependencies. This generates an analysis-report.md with an updated state to confirm deployment readiness.

Validation may miss inconsistencies if spec.md, plan.md, or tasks.md contain orphaned artifacts or unresolved dependency conflicts. Enforcing constitution-based risk checks ensures breaking-change detection identifies gaps before deployment.