bmad-retrospective

Facilitate epic-level retrospectives and track action items with assigned owners.

Updated Sep 27, 2025
One-click install
npx skills add https://github.com/Cbanzaime23/Booking-System --skill bmad-retrospective-cbanzaime23
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/Cbanzaime23/Booking-System/tree/main/.agent/skills/bmad-retrospective
Command: npx skills add https://github.com/Cbanzaime23/Booking-System --skill bmad-retrospective-cbanzaime23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-epic retrospectives are often ad-hoc, blame-prone, and fail to translate lessons into concrete actions. This Skill provides a structured, safe workflow to surface insights, capture action items, and track ownership across teams.

Core Features & Use Cases

  • Structured retrospectives: Facilitates epic-level reviews with a clear input/output rhythm and facilitator prompts.
  • Action-item tracking: Ensures accountability with assigned owners and status updates.
  • Next-epic alignment: Previews upcoming work to promote continuity and learning.
  • Blameless culture: Encourages psychological safety and evidence-based discussion.

Quick Start

Kick off a retrospective session with the project team and follow the guided workflow to capture lessons and assign owners.

Frequently Asked Questions about bmad-retrospective

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

FAQPage Schema
How do I run a blameless retrospective for an agile software project?▼

Run a blameless retrospective by using a structured workflow that surfaces epic-level insights through evidence-based discussion and facilitator prompts, ensuring psychological safety while capturing lessons learned.

What is the best way to track action items and ownership after a sprint retrospective?▼

Track action items after a sprint retrospective by assigning clear ownership and status updates within a structured documentation format, ensuring accountability for lessons learned across the team.

How do I facilitate cross-functional feedback during epic-level reviews?▼

Facilitate cross-functional feedback during epic-level reviews by applying a configurable workflow with persistent context, capturing story-level insights from all team members to improve future delivery.

Can I use this retrospective workflow to align lessons learned with upcoming epics?▼

Yes, you can align lessons learned with upcoming epics by previewing next-epic work within the retrospective workflow, promoting continuity and translating past insights into repeatable improvements.

Do I need any specific dependencies to configure this agile retrospective workflow?▼

No specific dependencies are required to configure this agile retrospective workflow, allowing you to implement structured documentation and repeatable improvements directly within your software projects.

Why do post-epic retrospectives fail to translate lessons into concrete actions?▼

Post-epic retrospectives fail when they are ad-hoc and blame-prone, but applying a structured, safe workflow surfaces insights, captures action items, and tracks ownership across teams for concrete improvements.