bmad-retrospective

Automates structured, blame-free retrospective workflows for agile sprint teams.

Updated May 5, 2026
One-click install
npx skills add https://github.com/devalexanderdaza/bmad-any --skill bmad-retrospective-devalexanderdaza
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/devalexanderdaza/bmad-any/tree/main/.agents/skills/bmad-retrospective
Command: npx skills add https://github.com/devalexanderdaza/bmad-any --skill bmad-retrospective-devalexanderdaza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unstructured, unproductive retrospectives often fail to capture actionable lessons or connect insights to future work, leading teams to repeat mistakes and miss improvement opportunities. This Skill automates a structured, blame-free retrospective workflow tailored for agile software development teams.

Core Features & Use Cases

  • Automated Epic Discovery: Identifies the correct completed epic to review by checking sprint status files, with fallbacks to user input or story folder scanning if status data is missing.
  • Cross-Story Pattern Analysis: Reviews all epic story records to surface recurring struggles, technical debt, review feedback, and breakthrough moments across the team's work.
  • Retrospective Continuity: Checks previous epic retrospectives to track action item follow-through, lesson application, and process improvement effectiveness over time.
  • Next Epic Preparation: Previews the upcoming epic to identify dependencies on completed work, technical prerequisites, and preparation gaps to reduce future blockers.
  • Use Case: A team that just finished a 5-story user authentication epic can use this Skill to run a structured retro that surfaces database migration delays, verifies if last epic's documentation action items were completed, and flags needed API setup work for the next payment processing epic.

Quick Start

Use the bmad-retrospective skill to run a structured retrospective for your team's most recently completed epic and generate actionable, blame-free lessons for future work.

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 for my agile team?

Post-epic retrospectives analyze completed epic story records to surface recurring struggles, technical debt, and breakthrough moments. They connect these insights to future work by tracking previous action item follow-through and identifying preparation gaps for upcoming epics.

Can I use sprint planning artifacts for retrospective continuity checks?

Yes, retrospective continuity checks integrate directly with existing sprint planning artifacts, including sprint status files, story records, and epic documentation. This verifies if previous action items were completed and tracks process improvement effectiveness over time.

What's the best way to track technical debt discovered during sprint reviews?

Track technical debt discovered during sprint reviews through cross-story pattern analysis that surfaces recurring struggles across all epic story records. This approach captures actionable improvements and flags needed technical prerequisites for future epics to reduce blockers.

Does automated epic discovery work if my sprint status files are missing?

Automated epic discovery works even when sprint status files are missing by falling back to user input or scanning story folders. This ensures the retrospective workflow proceeds correctly to identify the completed epic for review.

How do I facilitate blame-free team retrospectives that capture actionable improvements?

Facilitate blame-free team retrospectives by automating a structured workflow that analyzes cross-story patterns and tracks action item follow-through. This captures actionable improvements by focusing on process gaps and technical dependencies rather than individual team member performance.