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 and decide how to respond. This Skill guides that analysis and produces an actionable Sprint Change Proposal. ## Core Features & Use Cases - Systematic Impact Analysis: Walks through a six-section checklist covering trigger context, epic impact, artifact conflicts, and path-forward evaluation. - Structured Change Proposals: Drafts explicit before/after edit proposals for stories, GDD, narrative, architecture, and UI/UX documents. - 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: A developer discovers a technical limitation that invalidates a planned epic. Run this workflow to assess the blast radius, choose between direct adjustment, rollback, or MVP scope review, and generate a proposal document for approval. ## Quick Start Ask the agent to correct course and analyze the impact of the issue you just discovered on the current sprint plan.
