skills.rest
Rinzler78
Rinzler78COMMUNITY
Explore all skills by this author →
GitHub

bmad-retrospective

Analyze completed epic work and story records to identify recurring issues and prepare follow-up actions.

1|Updated Dec 22, 2022
Search Tags:#retrospective#software delivery#lessons learned#action items#epic review#team facilitation
One-click install
npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-retrospective-rinzler78
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-retrospective
Source: https://github.com/Rinzler78/osmosis-launcher/tree/main/.agents/skills/bmad-retrospective
Command: npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-retrospective-rinzler78

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams run a structured retrospective after completing an epic, turning scattered notes and memories into clear lessons, action items, and preparation for the next round of work.

Core Features & Use Cases

  • Epic discovery and validation: Identifies the completed epic, checks whether the work is actually done, and flags partial completion when needed.
  • Deep retrospective analysis: Reviews story records for recurring struggles, review feedback, technical debt, testing issues, and collaboration patterns.
  • Continuity and next-step planning: Compares the current epic against the previous retrospective and previews the next epic for dependencies, risks, and preparation needs.
  • Facilitated team discussion: Guides a psychologically safe, blame-free conversation with roles and turn-taking, keeping the discussion grounded in concrete examples.

Quick Start

Ask the skill to run a retrospective for the epic you just completed, and it will guide the team through review, lessons learned, and next-epic preparation.

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 for my software delivery team?▼

Run a retrospective by analyzing completed project artifacts like sprint status files and story records to detect recurring patterns. This skill validates epic completion and guides the team through a structured, blame-free discussion to extract actionable lessons learned.

What project artifacts do I need to facilitate a retrospective with action items?▼

Facilitating a retrospective with action items requires structured project artifacts including sprint status files, story records, previous retrospective notes, and planning documents. These inputs enable epic validation, story-level pattern detection, and continuity tracking for effective team facilitation.

Can I use completed story records to detect recurring technical debt and testing issues?▼

Yes, you can use story records to detect recurring technical debt and testing issues. The skill reviews story records to identify review feedback, collaboration patterns, and technical struggles, grounding the blame-free retrospective discussion in concrete project examples.

How does a blame-free retrospective handle continuity from prior epic reviews?▼

A blame-free retrospective handles continuity by comparing current epic outcomes against previous retrospective notes. This continuity tracking highlights resolved issues and previews the next epic, identifying dependencies, risks, and preparation needs for upcoming software delivery work.

When should I not use an automated retrospective review for software delivery?▼

You should not use an automated retrospective review when structured project artifacts like sprint status files, story records, or planning documents are missing. Without these inputs, the skill cannot perform epic validation, pattern detection, or continuity tracking accurately.

Related Skills

Explore More Software Engineering Skills→
devalexanderdazadevalexanderdaza

bmad-retrospective

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

Community
Advanced
imonmiimonmi

bmad-sprint-status

Summarizes sprint progress and risks from sprint-status.yaml files.

Community
Advanced
mol4mol4
1

bmad-sprint-planning

Generate sprint-status.yaml from BMAD epic markdown files and story artifacts.

Community
Advanced
Soul-Brews-StudioSoul-Brews-Studio
116

retrospective

Capture retrospective notes and generate concise lessons-learned summaries via /rrr alias.

Official
Basic