bmad-retrospective

Synthesize development logs and sprint data into structured post-epic retrospectives.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the challenge of conducting inconsistent or emotionally charged post-epic reviews by providing a structured, data-backed framework that focuses on systemic improvement rather than individual blame.

Core Features & Use Cases

  • Automated Epic Discovery: Intelligently identifies completed epics by analyzing sprint status and file artifacts.
  • Pattern Recognition: Synthesizes dev notes, review feedback, and velocity trends across multiple stories to surface actionable insights.
  • Continuity Tracking: Automatically cross-references previous retrospective action items to ensure team commitments are honored and lessons are applied.

Quick Start

Initiate the retrospective process by telling the assistant to run a retrospective for the most recently 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 a structured post-epic retrospective using sprint data?

Run a structured post-epic retrospective by synthesizing development logs, sprint status, and historical project data. The process identifies systemic bottlenecks, tracks technical debt, and measures velocity improvements to generate objective, action-oriented team reviews.

What is the best way to track technical debt and systemic bottlenecks after an epic?

Track technical debt and systemic bottlenecks by synthesizing dev notes, review feedback, and velocity trends across multiple stories. This pattern recognition approach surfaces actionable insights for continuous team improvement.

Can I automate epic discovery for agile retrospectives from project artifacts?

Automate epic discovery by intelligently analyzing sprint status files and file artifacts. The retrospective process automatically identifies completed epics to initiate data-driven, blame-free team reviews.

How do you ensure continuity of action items across multiple sprint retrospectives?

Ensure continuity of action items by automatically cross-referencing previous retrospective commitments. Continuity tracking verifies that team lessons are applied and honored throughout the software development lifecycle.

Do I need specific planning artifacts to generate a data-driven post-mortem?

You need access to project planning artifacts and sprint status files to generate a data-driven post-mortem. These inputs provide the objective development logs and historical project data required for accurate analysis.

Why does my agile retrospective become emotionally charged instead of focusing on improvement?

Agile retrospectives become emotionally charged without a structured, data-backed framework. By synthesizing development logs and velocity trends, the process shifts focus to systemic improvement rather than individual blame.