What problem does it solve? When a significant issue emerges mid-sprint, teams lack a structured way to evaluate its impact across planning artifacts and decide how to respond. This Skill guides a systematic change analysis and produces a formal Sprint Change Proposal with clear handoff routing. ## Core Features & Use Cases - Impact Analysis Checklist: Works through an interactive checklist covering trigger context, epic impact, artifact conflicts (PRD, architecture, UX), and path-forward evaluation. - Structured Change Proposals: Drafts explicit before/after edit proposals for stories, PRD sections, architecture, and UX specs, in incremental or batch review mode. - Scoped Handoff Routing: Classifies the change as Minor, Moderate, or Major and routes it to the Developer, Product Owner, or PM/Architect accordingly. - Use Case: During implementation you discover the chosen authentication approach cannot support a required 2FA regulation. Run this workflow to assess the impact on epics and the PRD, evaluate direct adjustment versus rollback versus MVP scope reduction, and generate an approved Sprint Change Proposal. ## Quick Start Say "correct course" or "propose sprint change" and describe the issue that triggered the need for change.
