bmad-retrospective

Facilitates post-epic retrospectives to extract lessons learned and prepare for the next epic.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/5onyy/essential-ai-agent-skills --skill bmad-retrospective-5onyy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/5onyy/essential-ai-agent-skills/tree/main/.cursor/skills/bmad-retrospective
Command: npx skills add https://github.com/5onyy/essential-ai-agent-skills --skill bmad-retrospective-5onyy

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 guides a facilitated retrospective that reviews completed stories, tracks follow-through on previous action items, and prepares the team for the next epic. ## Core Features & Use Cases - Epic Discovery and Verification: Automatically detects the completed epic from sprint-status files, verifies story completion, and handles partial retrospectives when stories remain pending. - Deep Story Analysis: Mines story files for dev notes, review feedback, technical debt, and recurring patterns across the epic to surface data-driven discussion topics. - Continuity Tracking: Loads the previous epic's retrospective and cross-references action items, lessons, and process improvements to measure follow-through. - Next Epic Preparation: Previews the upcoming epic, identifies dependencies on completed work, and flags preparation gaps and technical prerequisites. - Use Case: After finishing Epic 3 of a product build, run the retrospective to review what went well, assess whether Epic 2's action items were completed, and produce a retrospective document with action items for Epic 4. ## Quick Start Run a retrospective for the epic we just completed and generate the lessons-learned document.

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?▼

Invoke the skill by saying "run a retrospective" or "let's retro the epic". It detects the completed epic from the sprint-status file, asks you to confirm, then facilitates a structured review covering successes, challenges, and action items.

What inputs does the epic retrospective workflow need?▼

It reads the sprint-status YAML file, story markdown files for the epic, the previous epic's retrospective if one exists, plus architecture and PRD documents for context. A config file defines language, user name, and artifact paths.

Can I run a retrospective if some stories are not done?▼

Yes, but the workflow warns you first and lists pending stories. You can choose to complete remaining stories, run a partial retrospective, or refresh sprint planning before proceeding.

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 uses that follow-through as a discussion point about accountability.

What output does the retrospective produce?▼

It produces a retrospective analysis document containing concise insights, lessons learned, and action items with clear ownership, plus a next-epic preparation section covering dependencies and technical prerequisites.