skills.rest
AhmedKaram50
AhmedKaram50COMMUNITY
Explore all skills by this author →
GitHub

bmad-retrospective

Guide a Scrum team through a structured Epic retrospective workflow.

Updated Mar 18, 2026
Search Tags:#retrospective#agile#lessons learned#action items#sprint#epic#team facilitation
One-click install
npx skills add https://github.com/AhmedKaram50/research --skill bmad-retrospective-ahmedkaram50
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/AhmedKaram50/research/tree/main/shopify-builder/_bmad/bmm/workflows/4-implementation/bmad-retrospective
Command: npx skills add https://github.com/AhmedKaram50/research --skill bmad-retrospective-ahmedkaram50

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, collaborative framework to conduct post-epic retrospectives, helping teams extract lessons, surface improvements, and commit to actionable follow-ups.

Core Features & Use Cases

  • Guided retrospective workflow with roles, objectives, and facilitation notes.
  • Epics context integration: load completed epic data, compare with previous retros, and preview next epics.
  • Action-item tracking and accountability with cross-epic continuity.
  • Rich documentation of lessons learned, patterns, and improvement opportunities.

Quick Start

Run the bmad-retrospective workflow after epic completion to initiate a structured retrospective with the team.

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 agile retrospective after completing an epic?▼

To facilitate an agile retrospective after an epic, use a structured multi-step workflow covering discovery, analysis, previous retro integration, and next-epic planning to extract lessons and define actionable improvements.

What is the best way to track action items across multiple sprint retrospectives?▼

Tracking action items across sprint retrospectives requires loading completed epic data and comparing it with previous retros to ensure cross-epic continuity and accountability for measurable outcomes.

Can I run a retrospective during an epic instead of waiting for completion?▼

Yes, you can run a retrospective during or after epic completion to review completed work, compare with prior retrospectives, and plan next epic changes while the context is fresh.

How does a post-epic retrospective differ from a standard sprint retrospective?▼

A post-epic retrospective differs by integrating epic context, comparing lessons learned with previous retros, and planning changes for the next epic, rather than focusing solely on a single sprint.

What do I need to run a structured retrospective with defined roles and artifacts?▼

Running a structured retrospective requires assigning team roles, defining objectives, loading completed epic artifacts, and following facilitation notes to ensure measurable outcomes and documented lessons learned.

Related Skills

Explore More Software Engineering Skills→
geekdesign27geekdesign27

bmad-retrospective

Automates team retrospectives for software development epics with a defined workflow.

Community
Advanced
Yukine5377Yukine5377

bmad-retrospective

Facilitate structured epic retrospectives to capture lessons and plan improvements.

Community
Advanced
inbharataiinbharatai
22

sprint-planner

Facilitates agile sprint management with structured formats for planning, standups, and retrospectives.

Community
Basic
ImaginerLabsImaginerLabs

bmad-retrospective

Facilitate post-epic retrospectives to extract lessons and generate actionable items.

Official
Advanced