post-mortem

Facilitate blameless post-mortems with structured templates and action-item tracking.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/fabioc-aloha/AlexMedia --skill post-mortem-fabioc-aloha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: post-mortem
Source: https://github.com/fabioc-aloha/AlexMedia/tree/main/.github/skills/post-mortem
Command: npx skills add https://github.com/fabioc-aloha/AlexMedia --skill post-mortem-fabioc-aloha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams conduct blameless post-mortems after incidents to extract actionable learning and drive systemic improvements, instead of assigning blame.

Core Features & Use Cases

  • Structured incident reviews with a templated outline, timelines, and impact assessment.
  • Action-item tracking and ownership to ensure follow-through on improvements.
  • Facilitation guidance and anti-patterns to run productive retrospectives.

Quick Start

Draft a blameless post-mortem within 24 hours after an incident and publish it to the team.

Frequently Asked Questions about post-mortem

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

FAQPage Schema
How do I conduct a blameless post-mortem after an incident?▼

A blameless post-mortem facilitates incident reviews using a structured template to assess timelines and impact, extracting actionable learning for systemic improvements without assigning individual blame.

What is root cause analysis in the context of incident response?▼

Root cause analysis in incident response is a process facilitated by blameless post-mortems to structure learning and process improvements during retrospectives, ensuring incidents drive measurable system improvements rather than blame.

How do I track action items from a retrospective to ensure follow-through?▼

You track action items from a retrospective using an action-item framework that assigns clear ownership, ensuring measurable improvements identified during the post-incident review are actually implemented by the team.

When should I run an incident review and what do I need to prepare?▼

You should run an incident review within 24 hours after an incident occurs. Prepare by gathering incident timelines and impact data to populate a structured post-mortem template for the retrospective meeting.

What are common anti-patterns when facilitating post-incident retrospectives?▼

Common anti-patterns in post-incident retrospectives include assigning blame to individuals instead of focusing on systemic improvements, which this Skill avoids by providing facilitation guidance to keep reviews productive and blameless.

Can I use a structured runbook template for root cause analysis meetings?▼

Yes, you can use a structured template during root cause analysis meetings to guide incident reviews, map out timelines, assess impact, and generate measurable action items that drive systemic process improvements.