What problem does it solve? When a significant issue emerges mid-sprint—such as a technical limitation, new requirement, or failed approach—teams lack a structured way to assess its impact across the GDD, epics, architecture, and UX documents. This Skill guides a systematic change analysis and produces an actionable Sprint Change Proposal with clear handoff routing. ## Core Features & Use Cases - Impact Analysis Checklist: Walks through a six-section checklist covering trigger context, epic impact, artifact conflicts, path-forward options, and proposal components. - Structured Change Proposals: Drafts explicit before/after edit proposals for stories, GDD sections, narrative, architecture, and UI/UX artifacts, 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 Product Manager/Architect accordingly. - Use Case: During implementation, a developer discovers the chosen state management approach cannot support a planned feature. Invoke this Skill to assess which epics and architecture sections are affected, evaluate direct adjustment versus rollback versus MVP scope reduction, and produce an approved Sprint Change Proposal document. ## Quick Start Say "correct course" or "propose sprint change" and describe the issue that triggered the need for change.
