MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER DO NOT skip steps or change the sequence HALT immediately when halt-conditions are met Each andlt;actionandgt; within andlt;stepandgt; is a REQUIRED action to complete that step Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution Check {project-root}{output_folder}/stories/ for highest completed story Extract epic number from story (e.g., "Epic: 003") Read epic from {project-root}{output_folder}/prd/epic{number}.md List all stories for this epic in {project-root}{output_folder}/stories/ Check completion status of each story Extract key metrics (velocity, blockers encountered) Review epic goals and success criteria Compare actual outcomes vs. planned Note technical debt incurred Document architectural decisions made Read next epic from d{project-root}{output_folder}/prd/epic{next-number}.md Identify dependencies on completed work Note potential gaps or preparation needed Check for technical prerequisites

🔄 TEAM RETROSPECTIVE - Epic {{number}}: {{Epic Name}} Bob (Scrum Master) facilitating Epic Summary: - Completed: {{completed}}/{{total}} stories ({{percentage}}%) - Velocity: {{actual-points}} story points (planned: {{planned-points}}) - Duration: {{actual-sprints}} sprints (planned: {{planned-sprints}}) - Technical Debt: {{debt-items}} Next Epic Preview: Epic {{next-number}}: {{Next Epic Name}} - Dependencies on Epic {{number}}: {{dependencies}} - Preparation needed: {{preparation-gaps}} Team assembled for reflection: {{agents-based-on-story-records}} Focus: Learning from Epic {{number}} and preparing for Epic {{next-number}}

Each agent shares referencing actual story data What Went Well: Successes from completed stories, effective practices, velocity achievements What Could Improve: Challenges from story records, blockers that slowed progress, technical debt incurred Lessons Learned: Key insights for future epics, patterns to repeat or avoid Each agent addresses preparation needs Dependencies Check: What from completed epic is needed for next epic, any incomplete blocking work Preparation Needs: Technical setup required, knowledge gaps to fill, refactoring needed Risk Assessment: Potential issues based on experience, mitigation strategies Bob identifies patterns across feedback Synthesizes into team agreements Assigns ownership to action items Creates preparation sprint tasks if needed

📝 EPIC {{number}} ACTION ITEMS: {{numbered-action-items-with-owners}} 🚀 EPIC {{next-number}} PREPARATION SPRINT: {{preparation-tasks-with-timeline}} ⚠️ CRITICAL PATH: {{critical-dependencies-and-timeline}}

Testing Verification: Has full regression testing been completed? Deployment Status: Has epic been deployed to production? Business Validation: Have stakeholders reviewed and accepted deliverables? Technical Health: Is codebase in stable, maintainable state? Final Checks: Any unresolved blockers that will impact next epic? This task extends party-mode with retrospective-specific structure Bob (Scrum Master) facilitates the discussion ensuring psychological safety No blame, focus on systems and processes Everyone contributes with specific examples preferred Action items must be achievable with clear ownership End with team agreements and clear next steps Two-part format: Epic Review + Next Epic Preparation