bmad-retrospective

Facilitate a blame-free retrospective from completed epic execution and story records.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/cassioalexandre/agf --skill bmad-retrospective-cassioalexandre
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/cassioalexandre/agf/tree/main/_bmad/bmm/4-implementation/bmad-retrospective
Command: npx skills add https://github.com/cassioalexandre/agf --skill bmad-retrospective-cassioalexandre

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams run a blame-free post-epic retrospective that turns completed delivery into concrete lessons learned and actionable preparation for the next epic.

Core Features & Use Cases

  • Epic selection and validation: Detects the most recently completed epic using sprint-status, with fallbacks when status tracking is incomplete.
  • Structured facilitation outputs: Produces a two-part retrospective (Epic Review + Next Epic Preparation) with clear sections for insights and action items.
  • Continuity and learning loops: Loads the previous epic retrospective when available, cross-references commitments vs follow-through, and synthesizes system-level learnings from story records.
  • Team-grounded discussion guidance: Enforces party-mode dialogue formatting, role coverage, psychological safety, and system-focused reasoning.

Quick Start

Use the skill when you want to run a retrospective for the epic you just finished, and ask it to follow the workflow in workflow.md using your configured languages and inputs.

Frequently Asked Questions about bmad-retrospective

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an agile retrospective for a completed epic?

An agile retrospective analyzes completed epic execution by loading sprint status, PRD, and architecture documents to facilitate a blame-free review. It produces structured insights and actionable preparation guidance for the next epic.

What is a blame-free retrospective and how does it handle team facilitation?

A blame-free retrospective enforces psychological safety and system-focused reasoning through role-facilitated, party-mode dialogue. It synthesizes system-level learnings from completed story records while maintaining team psychological safety.

How do I extract lessons learned from completed sprint stories?

Extract lessons learned by cross-referencing previous retrospective commitments against follow-through and synthesizing system-level learnings from completed story records. This continuity loop ensures past commitments inform future epic preparation.

Can I use sprint status to automatically select which epic to review?

Yes, epic selection validates the most recently completed epic using sprint-status tracking, with fallback mechanisms when status records are incomplete. It loads the correct epic context documents automatically for retrospective analysis.

Do I need configuration files to run an epic retrospective?

You need configured planning artifacts including sprint status, epic, and architecture or PRD documents, plus the _bmad/bmm/config.yaml file defining party-mode dialogue and output language constraints. The skill reads these inputs to execute the retrospective workflow.