What problem does it solve? When a significant issue emerges mid-sprint, teams lack a systematic way to assess its impact across the PRD, epics, architecture, and UX artifacts. This Skill guides a structured change-management workflow that 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, proposal components, and final review. - Structured Change Proposals: Drafts explicit before/after edit proposals for stories, PRD sections, architecture, and UX documents, 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 Product Manager/Architect accordingly. - Use Case: A developer discovers a technical limitation that invalidates a planned story. Invoke this Skill to assess the impact on remaining epics, update sprint-status.yaml, and produce a Sprint Change Proposal for PO approval. ## Quick Start Ask the agent to correct course and analyze the impact of the issue you describe on the current sprint plan.