bmad-retrospective

Facilitate evidence-driven epic retrospectives with structured dialogue and action items.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill bmad-retrospective-enigmaicon-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/examples/BMAD-METHOD/src/bmm-skills/4-implementation/bmad-retrospective
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill bmad-retrospective-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) and scripts (resource) components.

What problem does it solve?

This Skill helps teams complete a structured, no-blame retrospective for an epic by extracting what happened from story artifacts and turning it into actionable improvements for the next epic.

Core Features & Use Cases

  • Epic selection and validation: Detects the most recently completed epic (prioritizing sprint-status) and confirms completion state before proceeding.
  • Evidence-driven insights: Loads story, architecture, and PRD inputs, then synthesizes themes from dev notes, review feedback, lessons learned, technical debt, and testing outcomes.
  • Facilitated team discussion: Guides psychologically safe dialogue (with a two-part format: epic review + next epic preparation) and produces concrete action items with ownership.
  • Continuity from prior retros: References the previous epic’s retrospective to track commitments, lessons applied, and missed opportunities.

Quick Start

Ask the system to run a retrospective for the epic that was just completed, and it will automatically identify the epic, analyze the supporting artifacts, and facilitate the team discussion.

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 epic retrospective using project artifacts?

To run an epic retrospective, the system automatically detects your most recently completed epic, loads relevant project documents like story details and PRDs, and synthesizes story-level patterns into actionable learnings for the team.

What is a no-blame retrospective and how does it work with epic reviews?

A no-blame retrospective facilitates psychologically safe dialogue by reviewing evidence from story artifacts, dev notes, and testing outcomes, synthesizing themes into actionable improvements rather than focusing on individual faults.

How do I track action items and lessons learned from a previous epic retro?

You can track action items from a previous epic retro through continuity checks that reference prior retrospective documents to monitor commitments, lessons applied, and missed opportunities during the current epic review.

Can I facilitate a team discussion to prepare for the next epic after a retro?

Yes, you can facilitate a team discussion to prepare for the next epic using a two-part format that covers the current epic review and transitions into planning and preparation for upcoming work.

Does the retrospective process require specific sprint status or project management setup?

The retrospective process requires completed epic status, prioritizing sprint-status to confirm completion state before proceeding with loading architecture, PRD inputs, and story artifacts for analysis.

What is the best way to capture technical debt and review feedback during an epic review?

The best way to capture technical debt and review feedback is through an evidence-driven synthesis that loads story inputs and extracts themes from dev notes and testing outcomes to produce concrete action items with ownership.