What problem does it solve? When a story fails, a technical dead-end appears, or new requirements emerge mid-project, teams need a structured way to assess the blast radius and decide how to respond. This Skill guides that analysis so changes are handled deliberately instead of ad hoc, minimizing wasted work while keeping epics, PRDs, and architecture documents consistent. ## Core Features & Use Cases - Structured Impact Analysis: Works through a change-checklist covering trigger context, epic impact, artifact conflicts (PRD, architecture, frontend spec), and path-forward options such as direct adjustment, rollback, or MVP re-scoping. - Sprint Change Proposal Generation: Drafts specific proposed edits to epics, stories, PRD sections, and architecture diagrams, then compiles them into an approval-ready proposal with an action plan and agent handoff. - Change Log Handoff: Emits ready-to-paste Change Log rows for each affected artifact so whoever applies the edits records document history correctly. - Use Case: A story fails because a chosen library cannot meet a requirement. Activate this Skill to assess which epics and artifacts are affected, evaluate adjusting versus re-scoping, and produce an approved proposal before any documents are touched. ## Quick Start Ask the agent to run change management on the failed story and produce a Sprint Change Proposal analyzing the impact on epics and the PRD.
