skills.rest
robotics-playground
robotics-playgroundOFFICIAL
Explore all skills by this author →
GitHub

bmad-retrospective

Extract patterns from past sprints and generate action items for epic retrospectives.

Updated Mar 18, 2026
Search Tags:#workflow#retrospective#agile#facilitation#epic#team-collaboration
One-click install
npx skills add https://github.com/robotics-playground/skills --skill bmad-retrospective-robotics-playground
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/robotics-playground/skills/tree/main/_bmad/bmm/workflows/4-implementation/bmad-retrospective
Command: npx skills add https://github.com/robotics-playground/skills --skill bmad-retrospective-robotics-playground

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Facilitates structured, blame-free retrospectives for completed epics, ensuring teams capture actionable lessons, concrete improvements, and continuity with future work.

Core Features & Use Cases

  • Guided initialization with configuration loading, artifact discovery, and role assignment to run consistent retrospectives.
  • Step-based workflow covering epic discovery, deep story analysis, review of previous epics, and preparation for the next epic.
  • Generates outputs such as action items, lessons learned, and continuity insights to inform upcoming work.

Quick Start

Initiate the retrospective workflow for a specific Epic by running the bmad-retrospective unit and confirming the target Epic number.

Frequently Asked Questions about bmad-retrospective

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

FAQPage Schema
How do I facilitate an epic retrospective for multiple completed sprints?▼

An epic retrospective analyzes completed epics with multiple stories and cross-functional teams to extract patterns and surface actionable improvements. It reviews prior retrospectives and prepares continuity insights for upcoming work.

What do I need to run a structured agile retrospective for cross-functional teams?▼

To run a structured agile retrospective, you need clear epic numbers, access to sprint-status and planning artifacts, and a defined facilitator role. These inputs enable the workflow to discover stories and generate follow-up actions.

How do I extract actionable lessons learned from a completed agile epic?▼

Extract actionable lessons by navigating a step-based workflow covering epic discovery and deep story analysis. This process surfaces concrete improvements and continuity insights to inform upcoming work and future planning.

Can I use retrospective insights to plan the next epic for my team?▼

Yes, retrospective insights directly support next-epic planning by generating continuity insights and action items from past sprints. The workflow explicitly includes preparing for the next epic as its final step.

Does the retrospective workflow review previous epic retrospectives before analyzing the current one?▼

Yes, the retrospective workflow includes a dedicated step to review previous epics before analyzing the current one. This ensures teams capture continuous improvements and maintain continuity with future work.

Related Skills

Explore More Product & Management Skills→
cassioalexandrecassioalexandre
2

bmad-retrospective

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

Community
Advanced
Rinzler78Rinzler78
1

bmad-sprint-status

Summarize sprint progress and recommend next workflow actions from sprint-status.yaml data.

Community
Advanced
devalexanderdazadevalexanderdaza

bmad-retrospective

Automates structured, blame-free retrospective workflows for agile sprint teams.

Community
Advanced
Soul-Brews-StudioSoul-Brews-Studio
116

retrospective

Capture retrospective notes and generate concise lessons-learned summaries via /rrr alias.

Official
Basic