post-mortems-retrospectives

Facilitate blameless post-mortems and retrospectives with structured templates and action trackers.

51|8|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/liqiongyu/lenny_skills_plus --skill post-mortems-retrospectives-liqiongyu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-mortems-retrospectives
Source: https://github.com/liqiongyu/lenny_skills_plus/tree/main/skills/post-mortems-retrospectives
Command: npx skills add https://github.com/liqiongyu/lenny_skills_plus --skill post-mortems-retrospectives-liqiongyu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams conduct blameless post-mortems and retrospectives, transforming failures and near-misses into actionable system learnings and concrete follow-through.

Core Features & Use Cases

  • Structured Workflow: Guides users through a 7-step process for incident postmortems and project/OKR retrospectives.
  • Template Generation: Provides copy-paste templates for briefs, agendas, timelines, contributing factors, action trackers, and kill criteria.
  • Blameless Facilitation: Offers checklists and rubrics to ensure reviews are evidence-based, action-oriented, and free from blame.
  • Use Case: After a critical service outage, use this Skill to run a blameless postmortem, identify root causes, create an action tracker with owners and due dates, and define criteria for preventing future incidents.

Quick Start

Run a blameless postmortem for the recent payments API incident.

Frequently Asked Questions about post-mortems-retrospectives

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

FAQPage Schema
How do I run a blameless postmortem after a critical incident?

Run a blameless postmortem by following a structured 7-step process to review the incident, identify contributing factors, and generate actionable decisions. This approach ensures reviews are evidence-based and free from blame.

What is the best way to structure a project retrospective?

The best way to structure a project retrospective is using a standardized template for briefs, timelines, and contributing factors. This ensures a thorough, constructive review process that transforms project debriefs into concrete action trackers.

How do I create an action tracker with owners and due dates for incident management?

Create an action tracker for incident management by using structured templates to assign owners and due dates to follow-through tasks. This ensures accountability and tracks kill criteria to prevent future incidents.

Can I use this for OKR retrospectives or is it only for incident reviews?

You can use this for OKR retrospectives as well as incident reviews and project debriefs. It provides structured templates and checklists to facilitate blameless reviews across all these scenarios, ensuring system learnings are derived.

What templates are needed to document contributing factors and kill criteria?

Templates needed to document contributing factors and kill criteria include briefs, timelines, action trackers, and structured checklists. These copy-paste formats ensure a comprehensive pack is produced for a thorough, action-oriented review.

Why does a blameless postmortem need kill criteria and checklists?

A blameless postmortem needs kill criteria and checklists to ensure the review process remains evidence-based and action-oriented. These components help define specific criteria for preventing future incidents and track actionable decisions effectively.