bmad-retrospective

Name: bmad-retrospective
Availability: InStock
Author: zerada

Facilitate epic retrospectives to review completed work and capture lessons learned.

Updated Jan 21, 2026

Search Tags:#project management #retrospective #lessons learned #project review #work review

Ready to run

npx skills add https://github.com/zerAda/RestaurantAgentAutomation --skill bmad-retrospective-zerada

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/zerAda/RestaurantAgentAutomation/tree/main/.opencode/skills/bmad-retrospective
Command: npx skills add https://github.com/zerAda/RestaurantAgentAutomation --skill bmad-retrospective-zerada

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill aids in conducting a review of completed work, capturing lessons learned, and planning for the next epic or addressing major issues.

Core Features & Use Cases

Review Work: Summarize and review the work completed during an epic.
Lessons Learned: Document and discuss lessons learned for future reference.
Next Epic Planning: Help in planning the next epic based on past experiences.
Issue Addressing: Identify and discuss major issues encountered during the epic.
Use Case: After an epic is completed, use this Skill to discuss what went well, what could be improved, and set the stage for the next project.

Quick Start

Use the bmad-retrospective skill to start 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 facilitate a project retrospective after completing an epic?▼

A project retrospective after completing an epic is facilitated by reading and executing a predefined workflow that captures user input and provides a structured review process to summarize work and discuss lessons learned.

What is the best way to document lessons learned during a project review?▼

The best way to document lessons learned during a project review is to use a structured retrospective workflow that captures user input, identifies major issues, and records what went well and what could be improved for future reference.

Can I use this retrospective process for software development workflows?▼

Yes, this retrospective process applies to software development workflows and general project management. It helps review completed work, address major issues, and plan the next epic based on past experiences.

How do I plan the next epic based on past project experiences?▼

To plan the next epic based on past project experiences, you conduct a structured end-of-epic review to capture lessons learned, discuss major issues, and use those insights to set the stage for the next project.

What should be included in an end-of-epic work review?▼

An end-of-epic work review should include a summary of completed work, a discussion of what went well, identification of areas for improvement, documentation of lessons learned, and addressing major issues encountered during the epic.

Do I need any specific dependencies to run this retrospective workflow?▼

No specific dependencies are required to run this retrospective workflow. The Skill operates independently using predefined scripts to capture user input and facilitate the structured review process.