What problem does it solve? When a significant issue emerges mid-sprint, teams lack a structured way to evaluate its impact across planning artifacts and decide how to respond. This Skill guides a systematic change-navigation workflow that analyzes the triggering issue against the PRD, epics, architecture, and UX documents, then produces an actionable Sprint Change Proposal with a clear implementation handoff. ## 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 Edit Proposals: Drafts explicit before/after change proposals for stories, PRD sections, architecture decisions, and UI/UX specifications, reviewed incrementally or in batch. - 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: A developer discovers mid-sprint that a chosen technology cannot meet a requirement. Invoke this Skill to assess which epics and stories are affected, evaluate direct adjustment versus rollback versus MVP scope reduction, and generate 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.
