bmad-retrospective

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

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/MathematicGuy/team-006-vin20k --skill bmad-retrospective-mathematicguy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/MathematicGuy/team-006-vin20k/tree/main/.agent/skills/bmad-retrospective
Command: npx skills add https://github.com/MathematicGuy/team-006-vin20k --skill bmad-retrospective-mathematicguy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often finish an epic without systematically capturing what worked, what failed, and which prior commitments were actually followed through, causing repeated mistakes and lost institutional knowledge. ## Core Features & Use Cases - Epic Discovery and Verification: Detects the completed epic from sprint-status files, verifies story completion, and warns when running a retrospective on an incomplete epic. - Deep Story Analysis: Mines story files for dev notes, review feedback, technical debt, and recurring patterns across the epic. - Continuity Tracking: Cross-references the previous epic's retrospective action items against current execution to measure follow-through. - Next Epic Preparation: Previews the upcoming epic, identifies dependencies on completed work, and lists preparation gaps. - Use Case: After finishing Epic 3, a project lead asks the agent to run a retrospective; the skill loads sprint status, analyzes all story records, checks Epic 2's retro commitments, and produces a retrospective document with action items. ## 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?▼

Invoke the skill by saying "run a retrospective" or "let's retro the epic" followed by the epic number. The workflow detects the completed epic from sprint-status.yaml, analyzes story records, and guides a facilitated team discussion.

How does the retrospective detect which epic was completed?▼

It first reads the sprint-status file to find the highest epic number with stories marked done, then asks you to confirm. If detection fails, it falls back to scanning story filenames in the implementation artifacts folder.

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

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

Does the retrospective track action items from previous retros?▼

Yes. It loads the previous epic's retrospective, extracts committed action items and lessons, then cross-references them against the current epic's story records to mark each as completed, in progress, or not addressed.

What inputs does the retrospective workflow require?▼

It requires a sprint-status YAML file, story markdown files under implementation artifacts, epic and architecture documents under planning artifacts, and a BMad config file defining user name, language, and skill level.