bmad-retrospective

Run a structured post-epic retrospective by guiding the team through epic review, synthesizing patterns across stories, and capturing action items with clear ownership to drive continuous improvement.

Extract lessons learned from an agile epic by reviewing completed story statuses, identifying recurring struggles and breakthroughs, and integrating velocity data with previous retro findings into a cohesive improvement plan.

Facilitate blame-free epic reviews by guiding the Scrum team through structured pattern synthesis, assessing outcomes and debt, and preparing for the next epic with measurable follow-through and evidence capture.

Ensure retrospective action items have clear ownership by assigning specific owners, capturing supporting evidence during the session, and linking improvements directly to next epic preparation for measurable follow-through.

Integrate velocity data and previous retrospective findings into epic planning by connecting past learning with current work, synthesizing patterns across stories, and preparing the next epic using rich context integration.

Conduct a post-epic retrospective immediately after epic completion to review outcomes, surface technical debt, synthesize cross-story patterns, and prepare actionable improvements for the next epic cycle.