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 to decide how to respond. This Skill guides that analysis and produces an actionable Sprint Change Proposal. ## Core Features & Use Cases - Impact Analysis Checklist: Systematically evaluates the triggering issue against epics, GDD, narrative, architecture, and UI/UX documents. - Path Forward Evaluation: Compares direct adjustment, rollback, and MVP scope review options with effort and risk estimates. - Structured Proposal & Handoff: Generates a Sprint Change Proposal with before/after edit proposals and routes implementation to Developer, PO, or PM/Architect based on scope. - Use Case: During sprint execution, a technical limitation invalidates a planned story. Run the workflow to assess which epics and artifacts are affected, draft concrete edits, and hand off an approved change plan. ## Quick Start Ask the agent to correct course by describing the sprint issue, for example: "Correct course — the physics engine cannot support the planned vehicle system, analyze the impact and propose changes."
