bmad-retrospective

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

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/shaahy/quicknav-desktop --skill bmad-retrospective-shaahy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/shaahy/quicknav-desktop/tree/main/A%20%E6%95%99%E7%A8%8B%E9%9B%86%E5%90%88/BMAD-METHOD%E6%8A%80%E8%83%BD%E9%80%9F%E6%9F%A5/source-v6.10.0/src/bmm-skills/4-implementation/bmad-retrospective
Command: npx skills add https://github.com/shaahy/quicknav-desktop --skill bmad-retrospective-shaahy

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: Detects the completed epic from sprint-status.yaml, 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: Loads the previous epic's retrospective and scores action items as completed, in progress, or not addressed. - Next Epic Preparation: Previews the upcoming epic, identifies dependencies on completed work, and lists preparation gaps. - Use Case: After finishing Epic 3, ask the agent to run a retrospective; it facilitates a no-blame 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 "let's retro the 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 after completing an epic?▼

Invoke the skill by saying "run a retrospective" or "let's retro the epic [number]". It detects the completed epic from sprint-status.yaml, verifies story completion, and guides a facilitated team discussion producing a retrospective document.

What inputs does the retrospective workflow need?▼

It reads sprint-status.yaml for story completion, story markdown files for dev notes and review feedback, the previous epic's retrospective for action-item follow-through, plus architecture and PRD documents for context.

Can I run a retrospective on an incomplete epic?▼

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 continuing.

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, cross-checking sprint-status and current story records for evidence.

What output does the retrospective produce?▼

It generates a retrospective analysis document with concise insights, lessons learned, and owned action items, then updates sprint-status. Output language and communication style follow the BMAD config settings.