harness-correct-course

To manage a sprint change across PRD, architecture, and UX artifacts, you can generate a structured Sprint Change Proposal. This process runs a checklist-driven impact analysis to identify conflicts and produces coordinated before/after edit plans for approval and handoff.

The best way to perform impact analysis for sprint scope changes is using a checklist-driven approach that reviews your planning artifacts. It cross-checks PRDs, epics, architecture, and UX specs to identify required edits and classify the change as minor, moderate, or major.

You generate a structured proposal for revising product requirements and epics by triggering a correct course workflow. It captures the issue summary, analyzes cross-artifact impacts, and outputs detailed edit plans for interactive or batch review.

Yes, you can use python3 to automate sprint change proposals and handoff planning. The workflow loads persistent facts and config, discovers planning artifacts, and routes execution handoff plans based on whether the scope change is minor, moderate, or major.

Yes, workflow orchestration supports incremental review for UX revisions. You can choose an interactive edit workflow to refine proposals one by one, or use batch review to evaluate all proposed UX revisions and architectural updates together.

You need a sprint change proposal for MVP scope adjustments when a proposed change may alter priorities or technical decisions. It translates a correct course moment into structured updates across your project artifacts to ensure safe implementation.