bmad-retrospective

Synthesize development logs and sprint status into retrospective insights.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill addresses the common struggle of conducting effective, objective post-epic reviews by automating the synthesis of development data and providing a structured, psychologically safe framework for team reflection.

Core Features & Use Cases

  • Automated Synthesis: Aggregates development notes, review feedback, and velocity patterns from project artifacts to surface key themes.
  • Continuity Tracking: Automatically links current retrospectives to previous action items and lessons learned to ensure long-term team growth.
  • Use Case: After completing a complex feature epic, use this skill to generate a summary of technical debt, identify recurring bottlenecks, and facilitate a structured discussion that prevents the team from repeating past mistakes.

Quick Start

Initiate the retrospective process for the most recently completed epic by telling the agent to run a retrospective.

Frequently Asked Questions about bmad-retrospective

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

FAQPage Schema
How do I automate the agile retrospective process for a completed epic?

To automate an agile retrospective, this Skill synthesizes development logs, sprint status files, and historical retrospective data to generate actionable insights. It aggregates project planning artifacts to surface key themes, technical debt, and recurring bottlenecks for team reflection.

What is a data-driven post-mortem in agile software development?

A data-driven post-mortem objectively reviews development data to improve team velocity and quality. This Skill provides a structured, blame-free framework by automatically synthesizing review feedback and velocity patterns from your project artifacts to facilitate systematic reflection.

Do I need specific project artifacts to run an automated sprint review?

Yes, running an automated sprint review requires access to project planning artifacts, sprint status files, and a structured repository of development stories. These inputs allow the Skill to accurately synthesize historical data and track continuity with previous action items.

How can I track continuity and past lessons learned during a retrospective?

You can track continuity and past lessons learned by linking current retrospectives to historical data. This Skill automatically connects your current post-epic review with previous action items and development logs to ensure long-term team growth and prevent repeating mistakes.

What is the best way to identify recurring bottlenecks after completing a feature epic?

The best way to identify recurring bottlenecks is using an automated retrospective Skill that analyzes velocity patterns and development logs. It aggregates this data to surface technical debt and recurring issues, providing a structured framework for process optimization.