bmad-retrospective

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

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/ncptuan/stock_backtest_project --skill bmad-retrospective-ncptuan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/ncptuan/stock_backtest_project/tree/main/.claude/skills/bmad-retrospective
Command: npx skills add https://github.com/ncptuan/stock_backtest_project --skill bmad-retrospective-ncptuan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams run a consistent, evidence-based retrospective after completing an epic, so lessons learned are captured, recurring problems are surfaced, and the next epic is better prepared.

Core Features & Use Cases

  • Epic discovery and completion checks: Identifies which epic to review from sprint status and validates whether its stories are actually done before proceeding.
  • Deep implementation analysis: Reviews story files, development notes, review feedback, testing insights, and technical debt to extract patterns and lessons.
  • Continuity and next-epic preparation: Compares current execution against the previous retrospective's action items and previews the next epic to identify risks, dependencies, and preparation gaps.
  • Use Case: After a product team finishes an implementation epic, use this Skill to facilitate a no-blame retrospective that summarizes wins, challenges, repeated review issues, unfinished commitments, and concrete action items for the next epic.

Quick Start

Ask the AI to run a retrospective for the just-completed epic and summarize lessons learned plus preparation for the next 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 retrospective after completing a sprint epic?

To run a structured retrospective after completing a sprint epic, load your project's sprint status and planning documents to validate story completion, then synthesize implementation artifacts and testing insights to extract actionable lessons learned.

What is epic retrospective facilitation and how does it analyze technical debt?

Epic retrospective facilitation is the process of reviewing completed epics to surface lessons learned and technical debt. It analyzes story records, development notes, and review feedback to identify recurring problems and unfinished commitments for better project preparation.

Can I use story records and sprint status to generate lessons learned for software delivery?

Yes, you can use story records and sprint status to generate lessons learned. The retrospective process validates story completion from sprint status and reviews implementation artifacts to extract patterns, wins, and challenges from your software delivery workflow.

How do I prepare for the next epic and assess project readiness after a sprint?

To prepare for the next epic, compare current execution against prior retrospective action items and preview upcoming planning documents. This identifies risks, dependencies, and preparation gaps to ensure your team is fully ready for the next sprint phase.

Does this retrospective analysis work without prior retrospective records or project configuration?

Prior retrospective records and project configuration are required to ensure continuity and accurate conflict-aware facilitation. Without these planning documents and previous action items, the analysis cannot effectively compare execution patterns or track follow-through.