bmad-correct-course

Sprint change management involves analyzing the cross-artifact impact of a proposed change across PRD, epics, stories, architecture, and UX artifacts. This process produces a structured Sprint Change Proposal with explicit before/after edits and an approval-gated handoff routing to safely steer sprints when plans change.

Architecture alignment impact analysis assesses how a requested sprint change affects existing architectural artifacts and planned epics. You need this checklist-based impact assessment when a significant execution change is triggered, ensuring evidence, conflicts, and path-forward rationale are captured consistently before proceeding.

To generate a sprint change proposal, trigger a 'correct course' workflow by providing the issue that caused the change and the desired outcome. The system discovers project artifacts, applies prioritization rules, and produces actionable before/after edit proposals routed based on scope classification as minor, moderate, or major.

Yes, you can assess UX updates and architecture conflicts using a guided, checklist-driven workflow. This interactive checklist ensures all evidence, cross-artifact conflicts, and path-forward rationale are captured consistently before the approval-gated final handoff routing is executed.

The best way to handle handoff and routing for major sprint scope changes is through an approval-gated final handoff process. The system classifies the change scope as minor, moderate, or major, then routes the structured Sprint Change Proposal to the appropriate downstream workflows based on that classification.