What problem does it solve? When a significant issue emerges mid-sprint, teams lack a systematic way to assess its impact across PRD, epics, architecture, and UX artifacts and decide how to respond. This Skill guides that analysis and produces an actionable Sprint Change Proposal with a clear implementation handoff. ## Core Features & Use Cases - Systematic Impact Analysis: Works through a structured checklist covering trigger context, epic impact, artifact conflicts (PRD, architecture, UI/UX), and path-forward evaluation. - Concrete Edit Proposals: Drafts before/after change proposals for stories, PRD sections, architecture, and UX specs, reviewed incrementally or in batch mode. - Scoped Handoff Routing: Classifies the change as Minor, Moderate, or Major and routes it to the right role (Developer, Product Owner, or PM/Architect). - Use Case: A developer discovers a technical limitation that invalidates a planned story. Run this workflow to assess which epics and documents are affected, choose between direct adjustment, rollback, or MVP scope reduction, and produce an approved proposal document. ## Quick Start Ask the agent to correct course for the issue discovered in the current story and produce a sprint change proposal.
