skills.rest
KatTate
KatTateCOMMUNITY
Explore all skills by this author →
GitHub

bmad-retrospective

Analyze completed epics and synthesize SMART action items from git history.

Updated Aug 27, 2026
Search Tags:#workflow#retrospective#agile#development process#lessons learned#epic review
One-click install
npx skills add https://github.com/KatTate/Bmad-for-Replit --skill bmad-retrospective
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/KatTate/Bmad-for-Replit/tree/main/.agents/skills/bmad-retrospective
Command: npx skills add https://github.com/KatTate/Bmad-for-Replit --skill bmad-retrospective

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of reviewing completed epics, identifying key learnings, and assessing their impact on ongoing and future work, ensuring continuous improvement in development cycles.

Core Features & Use Cases

  • Epic Analysis: Deep dives into completed stories, git history, and codebase health to extract actionable insights.
  • Learning Synthesis: Identifies lessons learned and checks follow-through on previous action items.
  • Future Planning: Assesses readiness for the next epic and synthesizes new action items.
  • Use Case: After completing a major feature epic, use this Skill to conduct a thorough retrospective, ensuring the team learns from the process and is better prepared for the next development phase.

Quick Start

Run the BMAD retrospective workflow for the 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 conduct an agile retrospective for completed epics?▼

An agile retrospective for completed epics analyzes git commit history and codebase health scans to extract learnings, assess impact on remaining work, and synthesize SMART action items for future sprints.

What is the best way to extract lessons learned from a completed development process?▼

Extracting lessons learned from a development process involves analyzing completed stories and git history to identify key learnings, check follow-through on previous action items, and assess readiness for the next epic.

Do I need specific configuration files to run the BMAD retrospective workflow?▼

Yes, running the BMAD retrospective workflow requires a workflow engine and specific configuration files to execute the epic review process and update sprint status correctly.

Can I use git commit history to generate SMART action items for sprint planning?▼

Yes, you can use git commit history and codebase health scans to synthesize SMART action items, updating sprint status and assessing readiness for the next development phase.

Does an epic review assess readiness for the next development phase?▼

Yes, an epic review assesses readiness for the next development phase by deep diving into completed stories and synthesizing new action items based on extracted insights.

Related Skills

Explore More Software Engineering Skills→
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

Epic Walkthrough Skill

Generate epic walkthrough documentation from state.yaml, epic-spec.md, sprint-plan.md, optimization-report.md, and git log.

Community
Advanced
GenEducationGenEducation

bmad-sprint-status

Summarizes sprint progress and flags delivery risks from sprint status records.

Official
Advanced
cookyscookys
10

retro

Analyze Git history and sprint data to generate structured retrospective reports.

Community
Advanced
mkalhitti-cloudmkalhitti-cloud
2

trading-knowledge-vault

Enforce mandatory lessons-learned reviews before NinjaTrader code changes.

Community
Advanced