skills.rest
cpliakas
cpliakasCOMMUNITY
Explore all skills by this author →
GitHub

conduct-postmortem

Conduct blameless incident postmortems and generate a 13-section document.

4|Updated Mar 11, 2026
Search Tags:#retrospective#action items#postmortem#incident analysis#incident management#blameless
One-click install
npx skills add https://github.com/cpliakas/claude-code-engineering-leaders --skill conduct-postmortem
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conduct-postmortem
Source: https://github.com/cpliakas/claude-code-engineering-leaders/tree/main/skills/conduct-postmortem
Command: npx skills add https://github.com/cpliakas/claude-code-engineering-leaders --skill conduct-postmortem

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of conducting blameless postmortems for incidents, ensuring thorough documentation and actionable insights.

Core Features & Use Cases

  • Incident Analysis: Gathers evidence, analyzes contributing factors, and synthesizes specialist input.
  • Structured Documentation: Produces a comprehensive, 13-section postmortem document adhering to blameless language rules.
  • Action Item Generation: Recommends actionable steps for preventing recurrence and improving processes.
  • Use Case: After a critical production outage, use this Skill to guide the team through a structured retrospective, identify systemic issues, and generate clear action items to prevent future occurrences.

Quick Start

Use the conduct-postmortem skill to start a postmortem for the recent database outage.

Frequently Asked Questions about conduct-postmortem

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

FAQPage Schema
How do I conduct a blameless postmortem after a production incident?▼

A blameless postmortem focuses on systemic issues rather than individual faults, using structured documentation to analyze incidents and generate actionable items that prevent recurrence and improve processes.

What is the best way to document incident analysis for a critical outage?▼

The best way to document incident analysis is generating a comprehensive 13-section postmortem document that adheres to blameless language rules and captures specialist input from the tech lead.

How do I generate actionable items from an incident retrospective?▼

You generate actionable items from an incident retrospective by analyzing contributing factors and synthesizing evidence into clear recommendations that prevent future occurrences and improve processes.

What should be included in a postmortem document for incident management?▼

A postmortem document for incident management should include 13 structured sections covering evidence collection, specialist input, incident analysis, and actionable items for recurrence prevention.

Can I use a structured format for blameless incident analysis without assigning blame?▼

Yes, you can use a structured format for blameless incident analysis that enforces blameless language rules while gathering evidence and specialist input to identify systemic issues rather than individual faults.

Related Skills

Explore More Software Engineering Skills→
kingdonkingdon
4

postmortem-author

Generate Sunkworks-style postmortem reports from Kubernetes incident data.

Community
Intermediate
irahardiantoirahardianto
150

incident-response

Guide production teams through incident response from severity classification to blameless postmortems.

Community
Advanced
Tommy-ywTommy-yw
539

common-incident-triage

Normalize production incident data and plan response actions.

Community
Intermediate
yusufcmgyusufcmg
1

postmortem-writing

Generates blameless postmortem documents with root cause analysis, timelines, and action items for incident reviews.

Community
Intermediate