bmad-retrospective

Facilitates post-epic retrospectives extracting lessons learned and action items from sprint artifacts.

Updated May 7, 2026
One-click install
npx skills add https://github.com/jgabriellima/deep-agent-skill --skill bmad-retrospective-jgabriellima
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/jgabriellima/deep-agent-skill/tree/main/skills/bmad-retrospective
Command: npx skills add https://github.com/jgabriellima/deep-agent-skill --skill bmad-retrospective-jgabriellima

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After completing an epic, teams often skip structured reflection, losing valuable lessons and repeating mistakes. This Skill runs a guided, multi-agent retrospective that mines story records, sprint status, and prior retrospectives to surface patterns, verify follow-through on past action items, and prepare for the next epic. ## Core Features & Use Cases - Epic Discovery and Verification: Detects the completed epic from sprint-status.yaml, validates story completion, and warns when running a retrospective on an incomplete epic. - Deep Story Analysis: Reads every story file to extract dev notes, review feedback, technical debt, testing insights, and recurring patterns across the epic. - Continuity Tracking: Loads the previous epic's retrospective and scores each prior action item as completed, in progress, or not addressed. - Next Epic Preparation: Previews the upcoming epic, maps dependencies on completed work, and lists preparation gaps and technical prerequisites. - Use Case: After finishing Epic 3 of a product build, ask the agent to run a retrospective; it facilitates a psychologically safe team dialogue, produces a retrospective document with action items and owners, and updates sprint-status. ## Quick Start Ask the agent to run a retrospective for the epic you just completed, for example by saying run a retrospective for epic 3.

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 retrospective for a completed epic?▼

Say "run a retrospective" or "let's retro the epic" to activate the workflow. It detects the completed epic from sprint-status.yaml, confirms with you, then guides a team discussion and produces a retrospective document with action items.

What inputs does the epic retrospective workflow need?▼

It reads sprint-status.yaml, story files for the epic, the epics document, architecture and PRD artifacts, and optionally the previous epic's retrospective. These are resolved from the planning and implementation artifacts directories configured in the BMad config.

Can I run a retrospective on an incomplete epic?▼

Yes, but the workflow warns you first, listing pending stories and recommending you finish them. If you confirm, it runs a partial retrospective and flags that lessons may be incomplete.

Does the retrospective track previous action items?▼

Yes. It loads the prior epic's retrospective and marks each committed action item as completed, in progress, or not addressed, then highlights applied lessons and missed opportunities in the discussion.

How do I customize the retrospective workflow behavior?▼

Edit the customize.toml workflow block or add team and user override TOML files under _bmad/custom. You can append activation steps, inject persistent facts, and set an on_complete hook without modifying the base skill.