bmad-retrospective

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

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/geekdesign27/travailleursisoles --skill bmad-retrospective-geekdesign27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/geekdesign27/travailleursisoles/tree/main/_bmad/bmm/workflows/4-implementation/bmad-retrospective
Command: npx skills add https://github.com/geekdesign27/travailleursisoles --skill bmad-retrospective-geekdesign27

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill facilitates a structured post-epic review to identify lessons learned, assess success, and prepare for future development cycles, ensuring continuous improvement.

Core Features & Use Cases

  • Facilitates Retrospectives: Guides a team through a post-epic review process.
  • Analyzes Past Performance: Extracts insights from completed stories and previous retrospectives.
  • Prepares for Future Epics: Identifies dependencies and preparation needs for the next development cycle.
  • Use Case: After completing a major software feature (epic), use this Skill to run a retrospective meeting, discussing what went well, what challenges were faced, and what actions to take for the next epic.

Quick Start

Use the bmad-retrospective skill to run a retrospective for the completed epic.

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 for a completed software epic?

To run an agile retrospective, this Skill automates the facilitation workflow by analyzing completed stories, identifying development patterns, and reviewing historical action items to drive continuous improvement.

What is the best way to identify lessons learned after a Scrum epic delivery?

The best way to identify lessons learned is to analyze completed sprint stories and previous retrospective data, which allows the system to extract insights on development struggles and successes for future preparation.

How do I prepare my team for the next epic during a post-epic review?

To prepare your team for the next epic, a post-epic review assesses previous action items and identifies upcoming dependencies and preparation needs, ensuring the development cycle starts with clear actionable improvements.

What data do I need to provide for an automated epic retrospective?

An automated epic retrospective requires loading project context, current sprint status, and historical retrospective data to provide comprehensive insights and accurately assess team performance.

Can I use this retrospective process to track continuous improvement across multiple sprints?

Yes, you can track continuous improvement because the process reviews previous action items and historical retrospective data alongside completed stories, ensuring patterns in struggles and successes inform future development cycles.

When should I conduct a retrospective for an agile epic?

You should conduct a retrospective immediately after completing a major software feature or epic, using the review to discuss what went well, what challenges were faced, and what actions to take next.