postmortem

Facilitate blameless post-mortem incident analysis to identify root causes and define preventative action items.

106|14|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/neurofoo/agent-skills --skill postmortem-neurofoo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/neurofoo/agent-skills/tree/main/postmortem
Command: npx skills add https://github.com/neurofoo/agent-skills --skill postmortem-neurofoo

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured, blameless framework for analyzing incidents, identifying root causes, and defining actionable steps to prevent future occurrences.

Core Features & Use Cases

  • Blameless Analysis: Focuses on systems and processes, not individuals, fostering a culture of learning.
  • Comprehensive Reporting: Guides users through documenting incident timelines, impact, root causes, and contributing factors.
  • Actionable Outcomes: Generates clear, assigned action items for immediate and short-term resolution.
  • Use Case: After a critical service outage, use this Skill to systematically document what happened, why it happened, and what needs to be done to ensure it doesn't happen again.

Quick Start

Use the postmortem skill to analyze the recent database outage.

Frequently Asked Questions about postmortem

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

FAQPage Schema
What is a blameless postmortem and how does it improve system reliability?

To conduct a blameless postmortem, systematically document the incident timeline, customer and business impact, and contributing factors. This structured analysis identifies root causes and generates clear, assigned action items to prevent future recurrence.

When do I need to perform an incident analysis for a service outage?

You need to perform an incident analysis after a critical event to systematically document the timeline and business impact. This ensures you accurately identify root causes and define preventative action items to avoid recurrence.

How do I document contributing factors and root causes during incident analysis?

You document contributing factors and root causes through a structured postmortem framework that guides you step-by-step through the incident timeline, business impact, and lessons learned to generate clear, assigned preventative action items.

What is the best way to define action items after identifying a root cause?

The best way to define action items after identifying a root cause is through a blameless postmortem process. It generates clear, assigned action items for immediate and short-term resolution, ensuring accountability and preventing future recurrence.

Can I use this postmortem framework for analyzing a database outage?

Yes, you can use this blameless postmortem framework to analyze a database outage. It supports comprehensive reporting of incident timelines, business impact, and root causes to generate preventative action items for any critical service disruption.