skills.rest
MazenMrad
MazenMradCOMMUNITY
Explore all skills by this author →
GitHub

bmad-retrospective

Facilitate epic retrospectives to extract lessons and track action items.

1|Updated Aug 3, 2025
Search Tags:#retrospective#agile#facilitation#epic#action-items#team-alignment#lessons-learned
One-click install
npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-retrospective-mazenmrad
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/MazenMrad/Obsidio/tree/main/.cursor/skills/bmad-retrospective
Command: npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-retrospective-mazenmrad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-epic reviews can be ad-hoc and hard to extract actionable lessons. This Skill provides a structured workflow to surface lessons, assign owners, and ensure continuity with prior retrospectives.

Core Features & Use Cases

  • Guided facilitation for epic retrospectives with roles, ground rules, and clear outcomes.
  • Automated extraction of lessons learned, action items, owners, and status tracking linked to epics and stories.
  • Next-epic readiness with dependency and risk surfacing to inform planning.

Quick Start

Initiate a retrospective for the current epic using the provided workflow and team data.

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 structured retrospective for a completed agile epic?▼

Run an epic retrospective by applying a guided facilitation workflow with defined roles and ground rules to surface actionable lessons learned and ensure team alignment after completion.

How do I track action items across multiple sprints after an epic review?▼

Track retrospective action items across multiple sprints by assigning owners, linking status updates to epics and stories, and referencing previous retrospective outcomes for continuity.

What is the best way to identify lessons learned from completed epics?▼

Identify lessons learned from completed epics by applying a retrospective workflow that surfaces actionable insights, assigns owners, and links tracking across epics and stories.

Can I forecast dependencies for upcoming epics during a retrospective?▼

Forecast dependencies for upcoming epics during a retrospective by surfacing next-epic readiness data and identifying risks to inform future sprint planning.

Do I need previous retrospective data to facilitate a new epic review?▼

Previous retrospective data is not required but is used to ensure continuity by referencing past lessons learned and action item statuses during the current epic review.

Related Skills

Explore More Product & Management Skills→
thuantan2060thuantan2060

bmad-retrospective

Discovers completed epics and analyzes story evidence to guide a no-blame retrospective.

Community
Advanced
amitmishra-bylddamitmishra-byldd

bmad-retrospective

Generate structured post-epic retrospective documents with action items.

Community
Advanced
skyoxuskyoxu

gds-retrospective

Facilitate structured post-epic retrospectives and generate consolidated reports with action items.

Community
Advanced
mol4mol4
1

bmad-retrospective

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

Community
Advanced