Identify the triggering story that revealed this issue Document story ID and brief description [ ] Done / [ ] N/A / [ ] Action-needed

Define the core problem precisely Categorize issue type: - Technical limitation discovered during implementation - New requirement emerged from stakeholders - Misunderstanding of original requirements - Strategic pivot or market change - Failed approach requiring different solution Write clear problem statement [ ] Done / [ ] N/A / [ ] Action-needed

Assess initial impact and gather supporting evidence Collect concrete examples, error messages, stakeholder feedback, or technical constraints Document evidence for later reference [ ] Done / [ ] N/A / [ ] Action-needed

HALT: "Cannot proceed without understanding what caused the need for change" HALT: "Need concrete evidence or examples of the issue before analyzing impact"

Evaluate current epic containing the trigger story Can this epic still be completed as originally planned? If no, what modifications are needed? [ ] Done / [ ] N/A / [ ] Action-needed

Determine required epic-level changes Check each scenario: - Modify existing epic scope or acceptance criteria - Add new epic to address the issue - Remove or defer epic that's no longer viable - Completely redefine epic based on new understanding Document specific epic changes needed [ ] Done / [ ] N/A / [ ] Action-needed

Review all remaining planned epics for required changes Check each future epic for impact Identify dependencies that may be affected [ ] Done / [ ] N/A / [ ] Action-needed

Check if issue invalidates future epics or necessitates new ones Does this change make any planned epics obsolete? Are new epics needed to address gaps created by this change? [ ] Done / [ ] N/A / [ ] Action-needed

Consider if epic order or priority should change Should epics be resequenced based on this issue? Do priorities need adjustment? [ ] Done / [ ] N/A / [ ] Action-needed

Check PRD for conflicts Does issue conflict with core PRD goals or objectives? Do requirements need modification, addition, or removal? Is the defined MVP still achievable or does scope need adjustment? [ ] Done / [ ] N/A / [ ] Action-needed

Review Architecture document for conflicts Check each area for impact: - System components and their interactions - Architectural patterns and design decisions - Technology stack choices - Data models and schemas - API designs and contracts - Integration points Document specific architecture sections requiring updates [ ] Done / [ ] N/A / [ ] Action-needed

Examine UI/UX specifications for conflicts Check for impact on: - User interface components - User flows and journeys - Wireframes or mockups - Interaction patterns - Accessibility considerations Note specific UI/UX sections needing revision [ ] Done / [ ] N/A / [ ] Action-needed

Consider impact on other artifacts Review additional artifacts for impact: - Deployment scripts - Infrastructure as Code (IaC) - Monitoring and observability setup - Testing strategies - Documentation - CI/CD pipelines Document any secondary artifacts requiring updates [ ] Done / [ ] N/A / [ ] Action-needed

Evaluate Option 1: Direct Adjustment Can the issue be addressed by modifying existing stories? Can new stories be added within the current epic structure? Would this approach maintain project timeline and scope? Effort estimate: [High/Medium/Low] Risk level: [High/Medium/Low] [ ] Viable / [ ] Not viable

Evaluate Option 2: Potential Rollback Would reverting recently completed stories simplify addressing this issue? Which stories would need to be rolled back? Is the rollback effort justified by the simplification gained? Effort estimate: [High/Medium/Low] Risk level: [High/Medium/Low] [ ] Viable / [ ] Not viable

Evaluate Option 3: PRD MVP Review Is the original PRD MVP still achievable with this issue? Does MVP scope need to be reduced or redefined? Do core goals need modification based on new constraints? What would be deferred to post-MVP if scope is reduced? Effort estimate: [High/Medium/Low] Risk level: [High/Medium/Low] [ ] Viable / [ ] Not viable

Select recommended path forward Based on analysis of all options, choose the best path Provide clear rationale considering: - Implementation effort and timeline impact - Technical risk and complexity - Impact on team morale and momentum - Long-term sustainability and maintainability - Stakeholder expectations and business value Selected approach: [Option 1 / Option 2 / Option 3 / Hybrid] Justification: [Document reasoning] [ ] Done / [ ] N/A / [ ] Action-needed

Create identified issue summary Write clear, concise problem statement Include context about discovery and impact [ ] Done / [ ] N/A / [ ] Action-needed

Document epic impact and artifact adjustment needs Summarize findings from Epic Impact Assessment (Section 2) Summarize findings from Artifact Conflict Analysis (Section 3) Be specific about what changes are needed and why [ ] Done / [ ] N/A / [ ] Action-needed

Present recommended path forward with rationale Include selected approach from Section 4 Provide complete justification for recommendation Address trade-offs and alternatives considered [ ] Done / [ ] N/A / [ ] Action-needed

Define PRD MVP impact and high-level action plan State clearly if MVP is affected Outline major action items needed for implementation Identify dependencies and sequencing [ ] Done / [ ] N/A / [ ] Action-needed

Establish agent handoff plan Identify which roles/agents will execute the changes: - Development team (for implementation) - Product Owner / Scrum Master (for backlog changes) - Product Manager / Architect (for strategic changes) Define responsibilities for each role [ ] Done / [ ] N/A / [ ] Action-needed

Review checklist completion Verify all applicable sections have been addressed Confirm all [Action-needed] items have been documented Ensure analysis is comprehensive and actionable [ ] Done / [ ] N/A / [ ] Action-needed

Verify Sprint Change Proposal accuracy Review complete proposal for consistency and clarity Ensure all recommendations are well-supported by analysis Check that proposal is actionable and specific [ ] Done / [ ] N/A / [ ] Action-needed

Obtain explicit user approval Present complete proposal to user Get clear yes/no approval for proceeding Document approval and any conditions [ ] Done / [ ] N/A / [ ] Action-needed

Confirm next steps and handoff plan Review handoff responsibilities with user Ensure all stakeholders understand their roles Confirm timeline and success criteria [ ] Done / [ ] N/A / [ ] Action-needed

HALT: "Cannot proceed to proposal without complete impact analysis" HALT: "Must have explicit approval before implementing changes" HALT: "Must clearly define who will execute the proposed changes"