skills.rest
JaronTam
JaronTamCOMMUNITY
Explore all skills by this author →
GitHub

bmad-retrospective

Synthesize lessons from story records and documentation for post-epic reviews.

Updated May 22, 2026
Search Tags:#retrospective#post-mortem#team collaboration#epic review#lesson learning
One-click install
npx skills add https://github.com/JaronTam/SDONE --skill bmad-retrospective-jarontam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/JaronTam/SDONE/tree/main/.agents/skills/bmad-retrospective
Command: npx skills add https://github.com/JaronTam/SDONE --skill bmad-retrospective-jarontam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, python3-pip, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The bmad-retrospective Skill simplifies post-epic reviews by extracting lessons and preparing for future success, reducing time spent on post-mortem analysis and enhancing team collaboration.

Core Features & Use Cases

  • Epic Review: Facilitates a comprehensive review of completed epics, extracting insights from stories and documentation.
  • Retrospective Analysis: Synthesizes patterns from stories, identifying common struggles, recurring feedback, and lessons learned.
  • Continuous Improvement: Integrates learnings from past retrospectives and identifies dependencies for upcoming work.
  • Use Case: Use the bmad-retrospective Skill after a project's completion to discuss what went well, what challenges were encountered, and to prepare for the next epic.

Quick Start

Run the bmad-retrospective skill with the command 'bmad-retrospective run'.

Frequently Asked Questions about bmad-retrospective

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

FAQPage Schema
How do I conduct a post-epic retrospective to extract lessons from story records?▼

To conduct a post-epic retrospective, you can use a Skill to synthesize insights from story records and documentation, identifying common struggles and recurring feedback to guide team improvement and future sprint planning.

What is the best way to analyze completed epics for continuous improvement?▼

Analyzing completed epics for continuous improvement involves synthesizing patterns from stories and documentation to extract lessons learned, helping teams prepare for success in upcoming software development sprints.

Do I need Python to run a retrospective analysis on project documentation?▼

Yes, running this retrospective analysis requires Python 3 and python3-pip installed in your environment to facilitate the comprehensive review of project documentation and story records.

Can I integrate past retrospective learnings into upcoming sprint planning?▼

Yes, you can integrate learnings from past retrospectives into upcoming sprint planning by synthesizing previous insights and identifying dependencies to ensure continuous improvement in software development.

How does post-mortem analysis identify recurring struggles in team collaboration?▼

Post-mortem analysis identifies recurring struggles by synthesizing patterns from completed story records and documentation, extracting common feedback and lessons learned to enhance team collaboration.

Related Skills

Explore More Software Engineering Skills→
mol4mol4
1

bmad-retrospective

Generate structured retrospectives with lessons learned and action items for completed BMAD epics.

Community
Advanced
webn77webn77

retro

Analyze sprint completion data to generate retrospective documents with metrics and action items.

Community
Intermediate
devalexanderdazadevalexanderdaza

bmad-retrospective

Automates structured, blame-free retrospective workflows for agile sprint teams.

Community
Advanced
alleneeealleneee

break-loop

Generate structured post-mortem reports from debugging sessions.

Community
Advanced