bmad-retrospective

Generate structured retrospectives with lessons learned and action items for completed BMAD epics.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/mol4/BMAD-Board --skill bmad-retrospective-mol4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/mol4/BMAD-Board/tree/main/BMAD%20board/.agents/skills/bmad-retrospective
Command: npx skills add https://github.com/mol4/BMAD-Board --skill bmad-retrospective-mol4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams review a completed epic, surface what worked and what did not, and turn delivery experience into actionable improvement.

Core Features & Use Cases

  • Epic Review: Summarizes story-level outcomes, recurring blockers, review feedback, testing issues, and technical debt from a finished epic.
  • Continuity Analysis: Compares the current epic against the previous retrospective to check whether commitments were completed and lessons were applied.
  • Next-Epic Preparation: Scans upcoming work for dependencies, risks, and readiness gaps so the team can enter the next epic with better context.
  • Use Case: After finishing a sprint or epic, use this Skill to run a structured retrospective that captures lessons, assigns follow-up actions, and prepares the team for the next phase.

Quick Start

Ask the assistant to run a retrospective for the completed epic and use the project files to summarize lessons learned, action items, and preparation for the next epic.

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?

To run an agile retrospective for a completed epic, review story records and prior commitments to generate lessons learned, action items, and next-epic preparation. The process validates epic completion and synthesizes story-by-story patterns.

What is epic continuity analysis in a sprint retrospective?

Epic continuity analysis in a sprint retrospective compares the current completed epic against previous retrospective commitments. This checks whether past lessons were applied and if action items were completed, ensuring continuous delivery improvement.

How do I prepare for the next epic after delivery?

To prepare for the next epic after delivery, scan upcoming work for dependencies, risks, and readiness gaps. This next-epic preparation provides better context and identifies potential blockers before the team enters the next phase.

Can I use a structured retrospective to track technical debt from a finished epic?

Yes, you can use a structured retrospective to track technical debt from a finished epic. The review summarizes story-level outcomes, recurring blockers, testing issues, and technical debt, turning the delivery experience into actionable improvement items.

Does this retrospective process require epic completion validation?

Yes, this retrospective process requires epic completion validation before generating psychologically safe facilitation output. It ensures the epic is fully delivered before synthesizing story patterns and checking roadmap dependencies.