bmad-retrospective

Analyze development data to surface issues and lessons after epic completion.

Updated Dec 26, 2025
One-click install
npx skills add https://github.com/tiween/tiween --skill bmad-retrospective-tiween
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/tiween/tiween/tree/main/.agents/skills/bmad-retrospective
Command: npx skills add https://github.com/tiween/tiween --skill bmad-retrospective-tiween

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, resolve_customization.py, resolve_config.py, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill facilitates post-epic reviews, helping teams assess their success, extract lessons learned, and prepare for future projects.

Core Features & Use Cases

  • Post-Epic Review: Facilitates structured discussions to review completed work, identify successes, challenges, and lessons.
  • Automated Data Analysis: Analyzes story records, identifying common issues, review patterns, and lessons learned.
  • Dependency Identification: Identifies and analyzes dependencies between epics to help with future project planning.
  • User Input and Participation: Allows team members to participate and share their insights during the review process.
  • Use Case: After completing an epic, use this Skill to review the outcomes, discuss successes, and identify areas for improvement.

Quick Start

Use the bmad-retrospective skill to conduct a review of the last 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 a post-epic retrospective to identify lessons learned?

A post-epic retrospective reviews completed work to extract lessons learned by facilitating structured discussions and analyzing development story records to surface common issues, patterns, and successes for future projects.

What is the best way to analyze development data for project review patterns?

Analyzing development data for project review patterns involves automated examination of story records to identify common issues and historical outcomes, which helps teams improve execution and plan future dependencies.

Does this retrospective skill require python3 to run automated analysis?

Yes, the retrospective skill requires python3 along with specific configuration scripts to manage its automated data analysis and dependency identification processes.

Can I identify dependencies between completed epics for future project planning?

Yes, you can identify dependencies between completed epics to help with future project planning by analyzing historical outcomes and story records during the post-epic review process.

How do I facilitate team collaboration during a project review?

Facilitating team collaboration during a project review involves allowing team members to participate and share their insights, ensuring structured discussions surface challenges and successes from recent epic execution.

When do I need an automated post-epic review instead of manual discussion?

You need an automated post-epic review when managing large volumes of story records, as automated analysis surfaces hidden issues, patterns, and dependency relationships that manual discussions might overlook.