bmad-retrospective

Name: bmad-retrospective
Availability: InStock
Author: yukine5377

Facilitate structured epic retrospectives to capture lessons and plan improvements.

Updated Apr 12, 2026

Search Tags:#retrospective #agile #scrum #epic #continuous-improvement #lessons-learned

Ready to run

npx skills add https://github.com/Yukine5377/common --skill bmad-retrospective-yukine5377

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/Yukine5377/common/tree/main/.cursor/skills/bmad-retrospective
Command: npx skills add https://github.com/Yukine5377/common --skill bmad-retrospective-yukine5377

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-epic retrospectives are essential for turning delivery into learning. This guide provides a structured, blame-free framework to review completed epics, surface lessons, capture actionable improvements, and prepare for the next epic. It integrates findings from stories, previous retros, and team feedback into a cohesive improvement plan.

Core Features & Use Cases

Structured facilitation of Epic Review (completed status, lessons learned, debt, and outcomes) and Next Epic Preparation, with clear ownership and outcomes.
Pattern synthesis across stories (common struggles, recurring feedback, breakthroughs) to guide discussion and continuous improvement.
Rich context integration (previous retros, velocity data, dependencies) to connect past learning with current work and future planning.

Quick Start

Start a retrospective for a specific epic by saying run a retrospective for Epic X, and I will guide the team through the session.

Frequently Asked Questions about bmad-retrospective

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run a structured retrospective for a completed epic?▼

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.

What is the best way to extract lessons learned from an agile epic?▼

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.

How do I facilitate blame-free epic reviews with my Scrum team?▼

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.

How do I ensure retrospective action items have clear ownership and measurable follow-through?▼

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.

Can I integrate velocity data and previous retrospective findings into epic planning?▼

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.

When should I conduct a post-epic retrospective for continuous improvement?▼

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.