bmad-retrospective

Generate structured post-epic retrospective documents with action items.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/amitmishra-byldd/Bmad-Note-Maker --skill bmad-retrospective-amitmishra-byldd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/amitmishra-byldd/Bmad-Note-Maker/tree/main/_bmad/bmm/4-implementation/bmad-retrospective
Command: npx skills add https://github.com/amitmishra-byldd/Bmad-Note-Maker --skill bmad-retrospective-amitmishra-byldd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured facilitation workflow for post-epic reviews that surfaces lessons learned, assesses completion and quality, and produces clear, assignable action items while preserving psychological safety.

Core Features & Use Cases

  • Epic discovery & verification: Detects the completed epic using sprint status and story files, with prioritized fallbacks and user confirmation.
  • Deep story analysis: Synthesizes developer notes, QA feedback, technical debt, and review patterns across all stories to surface recurring issues and breakthroughs.
  • Continuity & planning: Integrates previous retrospectives and previews the next epic to identify dependencies and preparation gaps, producing a two-part output: Epic Review and Next Epic Preparation.
  • Facilitation-ready output: Produces concise retrospective documents, action items with owners, and authentic team-style dialogue for interactive sessions.

Quick Start

Ask the agent to "Run a retrospective for epic 4 and produce a concise retrospective with lessons learned, prioritized action items with owners, and a short next-epic preparation checklist".

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 to extract lessons learned?

Run a post-epic retrospective by analyzing sprint status, story records, previous retrospectives, architecture, and PRD documents to surface patterns, risks, and dependencies, generating a two-part document with assigned action items.

What is a post-epic retrospective and how does it assess agile epic completion?

A post-epic retrospective assesses epic completion and quality by synthesizing developer notes, QA feedback, and technical debt across stories to surface recurring issues and breakthroughs while preserving psychological safety.

Do I need PRD and architecture documents to conduct an agile retrospective?

Yes, conducting a structured retrospective requires access to project configuration and implementation artifacts, selectively loading epic and story files, PRD documents, and architecture records to identify dependencies and preparation gaps.

How do I generate actionable agile action items with owners from sprint records?

Generate agile action items by synthesizing dev and QA notes from sprint records into a concise retrospective document, producing achievable, assigned action items paired with a next-epic preparation checklist.

Can a retrospective integrate previous sprint reviews to preview the next epic?

Yes, a retrospective can integrate previous retrospectives and preview the next epic to identify dependencies and preparation gaps, producing a two-part output covering both epic review and next epic preparation.

What is the best way to surface technical debt and risks after completing a scrum epic?

The best way to surface technical debt and risks after completing a scrum epic is to synthesize developer notes and QA feedback across all stories, identifying recurring issues and dependencies to generate prioritized action items.