What problem does it solve? When a significant issue emerges mid-sprint, teams lack a systematic way to assess its impact across PRD, epics, architecture, and UX artifacts, leading to ad-hoc decisions and undocumented scope changes. ## Core Features & Use Cases - Impact Analysis Checklist: Walks through a six-section checklist covering trigger context, epic impact, artifact conflicts, and path-forward evaluation. - Structured Change Proposals: Produces a Sprint Change Proposal with issue summary, impact analysis, recommended approach, detailed before/after edits, and implementation handoff. - Scope-Based Routing: Classifies changes as Minor, Moderate, or Major and routes them to Developer, Product Owner, or Product Manager/Architect roles. - Use Case: A developer discovers an authentication requirement conflict mid-sprint; the workflow loads the PRD and epics, assesses affected stories, and produces an approved proposal routed to the right agent. ## Quick Start Say "correct course" or "propose sprint change" and describe the issue that triggered the need for a sprint change.