bmad-retrospective

Generates a blame-free retrospective for completed epics from planning and story artifacts.

36|16|Updated May 1, 2026
One-click install
npx skills add https://github.com/tronghieu/lumina-wiki --skill bmad-retrospective-tronghieu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/tronghieu/lumina-wiki/tree/main/.agents/skills/bmad-retrospective
Command: npx skills add https://github.com/tronghieu/lumina-wiki --skill bmad-retrospective-tronghieu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams run a post-epic retrospective that turns completed delivery work into actionable lessons learned and a well-prepared next epic, reducing repeated mistakes and improving execution clarity.

Core Features & Use Cases

  • Epic discovery & validation: Detects the most recently completed epic (preferring sprint-status) and verifies whether the epic is actually complete, optionally supporting a partial retrospective when needed.
  • Evidence-based retrospectives: Loads relevant planning, PRD, architecture, and story artifacts, then synthesizes patterns from dev notes, review feedback, testing insights, technical debt, and lessons found in story records.
  • Continuity with previous retros: Compares with the previous epic’s retrospective to assess follow-through, effectiveness of process changes, and status of technical debt without blame.
  • Party-mode facilitation: Facilitates team dialogue using a safe, no-blame format that actively involves the user in decision points and discussion flow.

Quick Start

Ask your assistant to run the bmad-retrospective for your most recently completed epic.

Frequently Asked Questions about bmad-retrospective

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

FAQPage Schema
How do I generate a retrospective for a completed epic?

To generate a retrospective for a completed epic, the skill discovers the epic, loads planning and story artifacts, and synthesizes recurring lessons and technical debt into structured discussion prompts.

What is a blame-free post-epic retrospective?

A blame-free post-epic retrospective is a facilitation workflow that turns completed delivery work into actionable lessons learned and a well-prepared next epic using safe, party-mode dialogue formatting.

How do I extract lessons learned and technical debt from project artifacts?

Extract lessons learned and technical debt by loading planning, PRD, architecture, and story artifacts, then synthesizing patterns from dev notes, review feedback, and testing insights.

Can I run a retrospective on a partially completed epic?

Yes, you can run a retrospective on a partially completed epic. The workflow validates completion status and optionally supports a partial retrospective when the epic is not fully done.

How does an epic review check continuity with previous retrospectives?

An epic review checks continuity by comparing with the previous epic's retrospective to assess follow-through, effectiveness of process changes, and technical debt status without blame.

Do I need a root SKILL entry to run retrospective workflow automation?

Yes, retrospective workflow automation requires a root SKILL entry with YAML name and description, using workflow resolution with customizable activation steps and configured artifact directories.