bmad-retrospective

Guide post-epic retrospectives and extract lessons from implementation stories.

2|2|Updated Feb 16, 2025

Search Tags:#retrospective #agile #lessons learned #story analysis #epic review #project improvement

Ready to run

npx skills add https://github.com/allaydesai/Trading-ntrader --skill bmad-retrospective-allaydesai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/allaydesai/Trading-ntrader/tree/main/.cursor/skills/bmad-retrospective
Command: npx skills add https://github.com/allaydesai/Trading-ntrader --skill bmad-retrospective-allaydesai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill facilitates comprehensive retrospective analysis after completing an epic, helping teams extract lessons, identify improvements, and ensure continuous learning.

Core Features & Use Cases

Guided retrospective workflow: Provides structured instructions for conducting system-focused reviews without blame.
Deep story analysis: Extracts technical challenges, review feedback themes, and lessons learned from detailed story records.
Prepares next epic insights: Analyzes dependencies, risks, and preparatory actions for upcoming work.
Use Case: After completing a large development effort, teams can use this Skill to ensure all lessons are documented and applied in future planning.

Quick Start

Ask the AI to help analyze your recent epic and its stories to document lessons learned and prepare for the next project phase.

Frequently Asked Questions about bmad-retrospective

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

FAQPage Schema

How do I run an agile retrospective after completing a large development epic?▼

To run an agile retrospective after an epic, use this Skill to guide your team through a structured, blameless review focused on system improvements. It structures the workflow to extract technical challenges and lessons learned from your completed implementation stories.

What is the best way to document lessons learned from recent agile project stories?▼

The best way to document lessons learned is through deep story analysis, which extracts technical challenges, review feedback themes, and dependency insights from detailed story records. This ensures continuous learning is captured for future planning.

Can I analyze upcoming epic dependencies and risks before starting the next project phase?▼

Yes, you can analyze upcoming epic dependencies and risks before the next phase. The Skill prepares next epic insights by evaluating preparatory actions and dependency requirements extracted from the completed work.

Does this retrospective process focus on system improvements without assigning blame?▼

Yes, the retrospective process focuses strictly on system improvements without assigning blame. It provides guided instructions for conducting system-focused reviews to ensure continuous improvement in your agile workflows.

When do I need to perform a post-epic review instead of a standard sprint retrospective?▼

You need a post-epic review when a large development effort concludes, requiring comprehensive analysis across multiple stories. It captures cross-story dependency insights and feedback themes that standard sprint retrospectives often miss.