What problem does it solve? When a significant issue emerges mid-sprint in a game development project, teams lack a structured way to assess its impact across the GDD, epics, architecture, and UX artifacts. 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: Works through a six-section checklist covering trigger context, epic impact, artifact conflicts, path-forward options, and handoff planning. - 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. - Scope-Based Handoff: Classifies the change as Minor, Moderate, or Major and routes it to the Developer, Product Owner, or PM/Architect accordingly. - Use Case: A developer discovers a technical limitation that invalidates a planned epic. The Skill loads all planning artifacts, evaluates direct adjustment versus rollback versus MVP scope reduction, and writes a dated Sprint Change Proposal document. ## Quick Start Ask the agent to correct course and analyze the impact of the issue discovered in the current sprint story.