bmad-retrospective

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-retrospective-asygnuz-s-a-s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/Asygnuz-S-A-S/one-star/tree/main/.claude/skills/bmad-retrospective
Command: npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-retrospective-asygnuz-s-a-s

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 reviews completed stories, checks 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 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 to ground the discussion in real evidence. - Continuity Tracking: Cross-references the previous epic's retrospective action items against current execution to measure follow-through and identify repeated mistakes. - Next Epic Preparation: Previews the upcoming epic, maps dependencies on completed work, and flags 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 discussion, produces a retrospective document with action items, 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" or "let's retro 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". It detects the completed epic from your sprint-status file, asks you to confirm, then facilitates a structured team discussion and produces a retrospective document.

How does the retrospective detect which epic was completed?▼

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

Can I run a retrospective on an incomplete epic?▼

Yes, but the skill warns you first by listing pending stories and recommending you finish them. If you confirm, it runs a partial retrospective and flags that some lessons may be missed until remaining stories are done.

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

It needs a sprint-status YAML file, story files in the implementation artifacts folder, and planning artifacts such as epics, PRD, and architecture documents. A BMad config file provides user name, language, and artifact paths.