skills.rest
baphled
baphledCOMMUNITY
Explore all skills by this author →
Website𝕏@baphledGitHub

retrospective

Facilitate blameless post-mortem analysis using structured formats like the 4Ls.

1|Updated Mar 5, 2026
Search Tags:#root cause analysis#retrospective#post-mortem#continuous improvement#workflow refinement#blameless analysis
One-click install
npx skills add https://github.com/baphled/dotopencode --skill retrospective-baphled
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/baphled/dotopencode/tree/main/skills/retrospective
Command: npx skills add https://github.com/baphled/dotopencode --skill retrospective-baphled

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of reflecting on past projects or incidents to identify areas for improvement, ensuring continuous growth and preventing recurring issues.

Core Features & Use Cases

  • Facilitates Blameless Analysis: Guides teams to focus on system failures rather than individual mistakes.
  • Drives Actionable Improvements: Ensures that every reflection session results in specific, assigned, and time-bound action items.
  • Post-Mortem Analysis: Helps reconstruct timelines and identify root causes for production incidents using methods like the "5 Whys".
  • Continuous Improvement: Supports regular team reflections (e.g., end-of-sprint) to refine workflows and capture successes.

Quick Start

Use the retrospective skill to facilitate a blameless post-mortem analysis for the recent production incident.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I facilitate a blameless post-mortem analysis for a production incident?▼

A blameless post-mortem reconstructs incident timelines and identifies root causes using methods like the 5 Whys. This Skill guides teams to focus on system failures rather than individual mistakes, ensuring actionable improvements.

What is the best way to run a continuous improvement retrospective at the end of a sprint?▼

A continuous improvement retrospective refines workflows and captures successes using structured formats like the 4Ls. This Skill drives regular team reflections to ensure every session results in specific, assigned, and time-bound action items.

How does root cause analysis work for preventing recurring project issues?▼

Root cause analysis identifies the underlying system failures behind recurring issues. This Skill supports structured techniques like the 5 Whys to analyze past work, ensuring continuous growth and preventing the same problems from happening again.

Can I use the 4Ls retrospective format to identify workflow improvements?▼

The 4Ls retrospective format helps teams reflect on what they Liked, Learned, Lacked, and Longed for. This Skill supports the 4Ls structure to drive regular workflow refinement and capture successful patterns for continuous improvement.

Does a blameless analysis still produce actionable outcomes if the team focuses only on system failures?▼

Blameless analysis ensures actionable outcomes by shifting focus from individual mistakes to system failures. This Skill guarantees that every reflection session results in specific, assigned, and time-bound action items for continuous growth.

Related Skills

Explore More Product & Management Skills→
bowiemaxbowiemax

retro

Facilitate structured sprint retrospectives and generate prioritized action items.

Community
Intermediate
alunadevalunadev
3

retro

Facilitate structured sprint retrospectives with Start/Stop/Continue, 4Ls, or Sailboat formats.

Community
Intermediate
microbus-iomicrobus-io
172

Adding a Metric

Add or modify microservice metrics in service.yaml with go generate.

Official
Intermediate
RyoMurakami1983RyoMurakami1983
2

furikaeri-practice

Facilitate structured retrospectives using KPT, YWT, 5 Whys, and SMART goals.

Community
Intermediate