What problem does it solve? When a significant change hits a project mid-development (a pivot, technical dead-end, missing requirement, or failed story), teams often react ad hoc and miss downstream impacts. This Skill provides a structured framework to analyze the change, assess ripple effects across epics and artifacts, and produce an approved Sprint Change Proposal. ## Core Features & Use Cases - Six-Section Assessment Framework: Walks through trigger analysis, epic impact, artifact conflict review, path-forward options, proposal drafting, and final approval. - Artifact Conflict Analysis: Systematically checks PRD, architecture documents, frontend specs, and deployment assets for conflicts caused by the change. - Path Forward Evaluation: Compares direct adjustment, rollback, and MVP re-scoping options with explicit trade-offs. - Use Case: A story fails because a chosen library cannot meet a core requirement. Use this checklist to evaluate whether to adjust future stories, roll back completed work, or re-scope the MVP, then draft a change proposal with clear agent handoffs. ## Quick Start Ask the agent to run the change navigation checklist for the issue discovered in the current story and produce a sprint change proposal.
