bmad-retrospective

Name: bmad-retrospective
Availability: InStock
Author: GenEd

Analyze completed epic work and prior commitments to generate retrospective lessons and action items.

Updated Mar 30, 2026

Search Tags:#retrospective #agile #lessons learned #action items #epic review #team process

Ready to run

npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-retrospective-geneducation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/GenEducation/GenedUIProject/tree/main/.gemini/skills/bmad-retrospective
Command: npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-retrospective-geneducation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams run a structured retrospective after completing an epic so they can understand what worked, what caused friction, and what to improve next.

Core Features & Use Cases

Epic review facilitation: Guides a complete retrospective conversation with team roles, psychological safety, and a no-blame focus.
Cross-epic learning: Compares the completed epic with prior retrospective commitments and upcoming epic needs to spot continuity, risks, and missed follow-through.
Actionable outcomes: Produces concise lessons learned, process improvements, and achievable action items with ownership for the next cycle.

Quick Start

Use the bmad-retrospective skill to review the completed epic and generate a concise retrospective with lessons learned, follow-up actions, and preparation notes for the next epic.

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 after completing an epic?▼

To run an agile retrospective after an epic, analyze completed work, recurring issues, and prior commitments. This structured review process requires complete epic context and story records to produce grounded lessons learned and actionable next-step guidance for the team.

What is an epic review and when do I need it?▼

An epic review is a facilitated post-epic retrospective analyzing outcomes and friction. You need this agile team review process when developers, product owners, QA, and architects require a structured discussion of process improvements and continuity between completed and upcoming work.

How do I generate action items with ownership from lessons learned?▼

To generate action items with ownership from lessons learned, analyze story records and previous retrospective history. This process compares completed epic outcomes against prior commitments, producing concise process improvements and achievable action items assigned for the next development cycle.

Can I compare current epic outcomes with prior retrospective commitments?▼

Yes, you can compare current epic outcomes with prior retrospective commitments. Cross-epic learning analyzes previous history and upcoming dependencies to spot continuity, risks, and missed follow-through, ensuring that process improvements are tracked and applied across agile cycles.

What do I need to prepare for a structured post-epic team review?▼

Preparing for a structured post-epic team review requires gathering complete epic context, story records, and previous retrospective history. These inputs allow the analysis of outcomes and recurring issues, ensuring the generated lessons learned and action items are grounded.

How does cross-epic learning improve team process continuity?▼

Cross-epic learning improves team process continuity by analyzing prior commitments and upcoming epic dependencies. This retrospective mechanism identifies missed follow-through and recurring issues, producing actionable guidance that aligns process improvements with future development needs.