skills.rest
deltatree
deltatreeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

bmad-retrospective

Analyzes completed stories and sprint status files to generate actionable improvement items for retrospectives.

Updated Mar 16, 2026
Search Tags:#retrospective#agile#continuous improvement#team collaboration#scrum#epic review
One-click install
npx skills add https://github.com/deltatree/wissensmanagement --skill bmad-retrospective-deltatree
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/deltatree/wissensmanagement/tree/main/_bmad/bmm/workflows/4-implementation/bmad-retrospective
Command: npx skills add https://github.com/deltatree/wissensmanagement --skill bmad-retrospective-deltatree

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill facilitates structured retrospectives after epic completion, helping teams identify successes, challenges, and actionable improvements for future work.

Core Features & Use Cases

  • Guided Facilitation: Guides a Scrum Master through a comprehensive retrospective process.
  • Data-Driven Insights: Analyzes completed stories, previous retrospectives, and upcoming epics to provide context.
  • Action Item Generation: Helps define clear, achievable action items for continuous improvement.
  • Use Case: After completing a major software epic, the Scrum Master uses this Skill to run a retrospective, ensuring all lessons learned are captured and that the team is prepared for the next development cycle.

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 after completing a major epic?▼

To run an agile retrospective, you analyze completed stories and project planning artifacts to identify successes and challenges, then generate actionable improvement items. This facilitates structured team reflection after epic delivery.

What is the best way to generate actionable improvement items from completed scrum stories?▼

The best way to generate actionable improvement items is by analyzing completed stories to identify challenges and successes. This data-driven retrospective process ensures lessons learned are captured for continuous improvement.

Does this epic retrospective process integrate with existing sprint status files?▼

Yes, the epic retrospective process integrates directly with sprint status files and project planning artifacts. This integration provides comprehensive context for analyzing completed stories and preparing the team for the next development cycle.

Why do I need a structured retrospective process for continuous improvement?▼

You need a structured retrospective process to systematically identify successes and challenges from completed work. This ensures continuous improvement by translating past epic delivery experiences into clear, achievable action items.

Related Skills

Explore More Software Engineering Skills→
ncptuanncptuan

bmad-retrospective

Discover completed epics, validate story status, and synthesize retrospective lessons.

Community
Advanced
phurynphuryn
25.0k

retro

Facilitate structured sprint retrospectives and generate prioritized action items with owners and deadlines.

Community
Intermediate
joekhosbayarjoekhosbayar

gds-retrospective

Consolidate post-epic learnings and action items with ownership and status.

Community
Advanced
inbharataiinbharatai
22

sprint-planner

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

Community
Basic