skills.rest
mschuerig
mschuerigCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

bmad-retrospective

Orchestrate epic retrospectives by loading data, validating completion, and guiding action planning.

Updated Feb 11, 2026
Search Tags:#retrospective#agile#lessons learned#action items#scrum#epic#team facilitation
One-click install
npx skills add https://github.com/mschuerig/peach-ios --skill bmad-retrospective-mschuerig
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/mschuerig/peach-ios/tree/main/_bmad/bmm/workflows/4-implementation/bmad-retrospective
Command: npx skills add https://github.com/mschuerig/peach-ios --skill bmad-retrospective-mschuerig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams conduct disciplined, blameless retrospectives after epic completion, surfacing lessons, action items, and improvement opportunities.

Core Features & Use Cases

  • Epic-level data synthesis from stories and sprint artifacts to illuminate patterns and coaching points.
  • Integration with previous retrospectives to track commitments and measure impact.
  • Guided discussions for next-epic preparation, risk detection, and action-item ownership across the team.

Quick Start

Initiate a retrospective by specifying the epic number to review; the workflow will load relevant data and begin facilitation.

Frequently Asked Questions about bmad-retrospective

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

FAQPage Schema
How do I conduct an epic retrospective after completing a large agile project?▼

An epic retrospective synthesizes completed sprint stories and planning artifacts to evaluate team performance. It guides agile Scrum teams through structured, blameless analysis to surface lessons learned and generate actionable improvement items.

What is the best way to track action items from previous agile retrospectives?▼

Tracking retrospective action items involves integrating past commitments with current epic data. This approach validates completion, measures the impact of previous decisions, and ensures documented actions have clear owners to improve future sprints.

How do I facilitate a blameless retrospective for my Scrum team?▼

Facilitating a blameless retrospective requires guiding teams through structured discussions focused on outcomes. It leverages sprint status and story records to identify patterns, detect risks, and document defensible decisions for future epic preparation.

Can I use sprint status and story records to prepare for an upcoming epic?▼

Yes, you can use sprint status and story records for next-epic preparation. Analyzing these agile artifacts illuminates coaching points, detects potential risks early, and helps teams establish ownership of action items before development begins.

What outcomes should a structured epic retrospective produce?▼

A structured epic retrospective produces actionable outcomes including documented lessons learned, assigned action items with owners, and defensible decisions. These results aim to surface team patterns and directly improve future epic execution.

Related Skills

Explore More Product & Management Skills→
co-cddoco-cddo
4

bmad-sprint-planning

Generate sprint-status.yaml from Markdown epic files and story data.

Official
Advanced
mol4mol4
1

bmad-retrospective

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

Community
Advanced
yunseo-kimyunseo-kim
1

sprint-planner

Plan Agile sprints with story estimation, capacity planning, and velocity tracking.

Community
Intermediate
tiweentiween

bmad-retrospective

Analyze development data to surface issues and lessons after epic completion.

Official
Advanced