bmad-retrospective

Facilitate structured post-epic retrospectives with story analysis and action items.

Updated May 23, 2026

Search Tags:#retrospective #agile #lessons learned #story analysis #epic review #team facilitation

Ready to run

npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-retrospective-diegosanchespereira1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/diegosanchespereira1/lavarapido/tree/main/lava-rapido/.agents/skills/bmad-retrospective
Command: npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-retrospective-diegosanchespereira1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams run structured retrospectives after completing an epic so they can capture what worked, what failed, and what to improve next.

Core Features & Use Cases

Epic completion validation: Confirms the epic is actually done before the retrospective begins, reducing the risk of reviewing incomplete work.
Deep cross-story analysis: Reviews story records to identify recurring struggles, review feedback patterns, technical debt, testing gaps, and breakthrough moments.
Continuity and planning support: Compares the current epic against the previous retrospective and previews the next epic to surface follow-through and preparation needs.
Use case: A product team finishes an implementation epic and uses this Skill to facilitate a psychologically safe discussion, capture lessons learned, and produce concrete action items for the next cycle.

Quick Start

Use the bmad-retrospective skill to review the completed epic you just finished and generate a concise retrospective with lessons learned and next-step action items.

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 a software epic?▼

This Skill facilitates epic retrospectives by validating epic completion, analyzing story records for recurring struggles, comparing against previous retrospectives, and synthesizing next-epic context to produce actionable improvements.

What is the best way to capture lessons learned from completed user stories?▼

The best way to capture lessons learned is by reviewing story records to identify recurring struggles, technical debt, and testing gaps, while maintaining strong psychological-safety guardrails during cross-functional team discussions.

Does this retrospective process require the epic to be fully completed?▼

Yes, this retrospective process requires epic completion validation to confirm the work is actually done before reviewing, reducing the risk of analyzing incomplete stories or capturing inaccurate lessons learned.

Can I compare current epic review feedback with previous retrospective action items?▼

Yes, this Skill performs continuity checks by comparing current epic review feedback against previous retrospectives to surface follow-through, ensuring past lessons learned inform current story analysis and actionable improvements.

How do I prepare my team for the next epic during a post-epic review?▼

To prepare your team for the next epic, this Skill performs next-epic context synthesis to preview upcoming work and surface preparation needs, ensuring actionable improvements from the retrospective inform future story planning.