skills.rest
ldk-hub
ldk-hubCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

bmad-retrospective

Analyze completed epic stories to extract patterns, root causes, and lessons learned.

Updated Apr 25, 2026
Search Tags:#retrospective#agile#facilitation#epic#team-learning#action-items
One-click install
npx skills add https://github.com/ldk-hub/broke-shopping --skill bmad-retrospective-ldk-hub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/ldk-hub/broke-shopping/tree/main/_bmad/bmm/4-implementation/bmad-retrospective
Command: npx skills add https://github.com/ldk-hub/broke-shopping --skill bmad-retrospective-ldk-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Retrospective workflow enables blameless, structured reviews of completed epics to extract lessons, surface root causes, and drive continuous improvement in delivery.

Core Features & Use Cases

  • Structured epic retrospectives that surface systemic issues, lessons learned, and actionable improvements.
  • Cross-functional data synthesis from epic/stories (Dev Notes, Code Reviews, QA feedback) to guide discussion.
  • Production of a concise retrospective document with assigned owners and follow-up items, plus a prep for the next epic.

Quick Start

Start the retrospective by activating the bmad-retrospective skill and guiding the team through Epic retrospective steps highlighted in the workflow.

Frequently Asked Questions about bmad-retrospective

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

FAQPage Schema
How do I run an agile retrospective for a completed epic?▼

Run an agile retrospective by analyzing completed epic stories to extract patterns and root causes, then producing a concise retrospective document with assigned owners and actionable follow-up items.

What is a blameless retrospective and how does it surface systemic issues?▼

A blameless retrospective is a structured review focusing on process rather than individuals, synthesizing cross-functional data like Dev Notes and QA feedback to surface systemic issues and lessons learned for future work.

How do I extract actionable improvement items from epic stories?▼

Extract actionable improvements by analyzing each story within a completed epic to identify patterns and root causes, translating these insights into follow-up actions with clear owners for continuous improvement.

Can I synthesize code review and QA feedback for team-learning?▼

Yes, you can synthesize code review and QA feedback alongside Dev Notes to guide retrospective discussion, extracting lessons learned to drive team-learning and continuous delivery improvement.

What's the best way to document action items with clear owners?▼

The best way to document action items is producing a concise retrospective document that captures root causes and assigns clear owners to specific follow-up actions for future work.

Does this retrospective workflow prepare the team for the next epic?▼

Yes, the retrospective workflow produces a concise document with follow-up items and includes a preparation step to guide the team's approach for the next epic.

Related Skills

Explore More Product & Management Skills→
josemariafsjosemariafs
3

bmad-retrospective

Facilitate blameless post-epic retrospectives and generate action items.

Community
Advanced
Yukine5377Yukine5377

bmad-retrospective

Facilitate structured epic retrospectives to capture lessons and plan improvements.

Community
Advanced
anderson-0anderson-0
4

retrospective

Facilitate post-epic retrospective reviews to extract lessons and define improvement actions.

Community
Advanced
89jobrien89jobrien
4

agile-ceremonies

Structure Agile standups, retrospectives, and sprint tracking with action items.

Community
Intermediate