bmad-retrospective

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

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill bmad-retrospective-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/Wizarck/nexandro/tree/main/skills/bmad-retrospective
Command: npx skills add https://github.com/Wizarck/nexandro --skill bmad-retrospective-wizarck

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 & Verification: Automatically detects the completed epic from sprint-status files, verifies all stories are done, and warns before running a partial retrospective. - 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 to check whether committed action items were completed. - Next Epic Preparation: Previews the upcoming epic, identifies dependencies on completed work, and flags preparation gaps. - Use Case: After finishing Epic 3 of a product build, say "run a retrospective" and the Skill facilitates a blameless team discussion, then produces a retrospective document with lessons learned and action items. ## Quick Start Ask the assistant to run a retrospective for the epic you just completed, for example by saying "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, verifies story completion, and guides a structured team discussion producing a retrospective document.

What inputs does the retrospective workflow need?▼

It reads the sprint-status YAML file, story markdown files for the epic, the epic definition, architecture and PRD documents, and optionally the previous epic's retrospective. These come from your planning and implementation artifacts directories.

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 instead. Partial retrospectives are flagged as potentially incomplete.

Does the retrospective track previous action items?▼

Yes. It loads the previous epic's retrospective and cross-references each committed action item against evidence in the current epic's story records, marking items as completed, in progress, or not addressed.

What output does the retrospective produce?▼

It generates a retrospective analysis document containing delivery metrics, success and challenge themes, lessons learned, technical debt items, action items with ownership, and preparation notes for the next epic.