skills.rest
Wizarck
WizarckCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

bmad-retrospective

Analyze completed epics and synthesize feedback into structured action items.

Updated Apr 26, 2026
Search Tags:#learning#retrospective#agile#facilitation#epic#process-improvement
One-click install
npx skills add https://github.com/Wizarck/iguanatrader --skill bmad-retrospective-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/Wizarck/iguanatrader/tree/main/skills/bmad-retrospective
Command: npx skills add https://github.com/Wizarck/iguanatrader --skill bmad-retrospective-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrospectives are essential for organizational learning but can be unstructured, blame-prone, and inconsistent across epics. This Skill provides a repeatable, blame-free framework to surface lessons, track action items, and connect learnings to future epics.

Core Features & Use Cases

  • Structured Epic retrospectives that capture successes, challenges, and patterns.
  • Action-item ownership tracking with evidence and status visibility.
  • Cross-functional synthesis of feedback from developers, QA, and product owners to guide next-epic planning.

Quick Start

Kick off a retrospective for the target epic and begin structured discussion to surface lessons learned.

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 post-epic retrospective to capture lessons learned?▼

Run a post-epic retrospective by analyzing completed epics, gathering cross-functional feedback, and synthesizing patterns to inform next-epic planning. This enforces a blame-free format with structured action items, ownership tracking, and evidence for continuous improvement.

What is the best way to track retrospective action items with clear ownership?▼

Track retrospective action items by enforcing a structured format for ownership and evidence visibility. This ensures repeatable learning by connecting synthesized feedback patterns directly to next-epic planning with accountable action items.

How do I gather cross-functional feedback for agile retrospective synthesis?▼

Gather cross-functional feedback by collecting inputs from developers, QA, and product owners. Synthesizing these perspectives surfaces actionable patterns to guide next-epic planning and drives continuous process improvement.

Can I use this retrospective framework to prevent blame during process improvement?▼

Yes, you can use this framework to prevent blame during process improvement. It provides a repeatable, blame-free structure to surface lessons, track action items, and connect learnings to future epics.

Do I need completed epic data to facilitate an agile retrospective?▼

Yes, you need completed epic data to facilitate an agile retrospective. The process analyzes completed epics and synthesizes feedback from developers, QA, and product to extract actionable lessons for future planning.

Related Skills

Explore More Software Engineering Skills→
GenEducationGenEducation

bmad-retrospective

Analyze completed epic work and prior commitments to generate retrospective lessons and action items.

Official
Advanced
Yukine5377Yukine5377

bmad-retrospective

Facilitate structured epic retrospectives to capture lessons and plan improvements.

Community
Advanced
legioncodeinclegioncodeinc
72

retrospective-stinger

Convert team feedback sessions into structured behavior-change workflows.

Official
Advanced
Lev-itLev-it

summarize-meeting

Extract key information from meeting transcripts into structured summaries.

Official
Intermediate