skills.rest
imonmi
imonmiCOMMUNITY
Explore all skills by this author →
GitHub

bmad-retrospective

Identify actionable insights from completed epics through a structured retrospective workflow.

Updated Mar 24, 2026
Search Tags:#retrospective#agile#scrum#facilitation#epic#team-learning#continuous-improvement
One-click install
npx skills add https://github.com/imonmi/INTER-EDU --skill bmad-retrospective-imonmi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/imonmi/INTER-EDU/tree/main/_bmad/bmm/workflows/4-implementation/bmad-retrospective
Command: npx skills add https://github.com/imonmi/INTER-EDU --skill bmad-retrospective-imonmi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and surface actionable insights from completed epics through a structured retrospective workflow.

Core Features & Use Cases

  • Structured epic retrospectives: captures wins, challenges, and action items with ownership.
  • Cross-functional alignment: links previous retros, next epic planning, and continuous improvement.
  • Data-backed decisions: synthesizes story-level patterns and notes blockers for future sprints.

Quick Start

Initiate a structured retrospective for the selected epic and guide the team through wins, challenges, and next steps.

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 my Agile team?▼

Facilitate an epic retrospective by guiding your Agile team through a structured workflow to review epic completion, capture wins and challenges, extract lessons, and document action items with clear ownership.

What is the best way to extract actionable insights from completed epics?▼

Extract actionable insights from completed epics by synthesizing story-level patterns, identifying blockers, and enforcing guardrails for psychological safety to ensure teams capture meaningful lessons for future sprints.

How does a structured epic retrospective link to continuous improvement?▼

A structured epic retrospective links to continuous improvement by connecting previous retrospective outcomes with next epic planning, ensuring cross-functional alignment on documented action items and next steps.

Can I use this retrospective workflow for Scrum sprint planning?▼

Yes, Scrum Masters, Product Owners, and developers can use this retrospective workflow to summarize epic outcomes, note blockers, and plan improvements that directly feed into the next sprint planning cycle.

What guardrails does this epic retrospective process enforce?▼

This epic retrospective process enforces guardrails for psychological safety, clear ownership of action items, and structured documentation of outcomes to ensure productive team-learning sessions.

When should I run a retrospective on a completed epic?▼

Run a retrospective on a completed epic when you need to review epic completion, synthesize story-level patterns, and align the cross-functional team on continuous improvements before the next cycle begins.

Related Skills

Explore More Product & Management Skills→
JingyiWngJingyiWng

bmad-retrospective

Conduct post-epic retrospectives from story files and sprint-status.yaml.

Community
Advanced
runchr-comrunchr-com

retro

Facilitate structured sprint retrospectives and generate prioritized action items.

Official
Intermediate
Hack23Hack23
235

product-management-patterns

Automate product management workflows for backlog grooming and sprint planning.

Official
Basic
legioncodeinclegioncodeinc
72

retrospective-stinger

Convert team feedback sessions into structured behavior-change workflows.

Official
Advanced