incident-postmortem

Name: incident-postmortem
Availability: InStock
Author: oalansilva

Draft incident postmortems with timeline, RCA, and action items.

Updated Dec 28, 2025

Search Tags:#timeline #reliability #postmortem #incident #blameless #rca #action-items

Ready to run

npx skills add https://github.com/oalansilva/crypto --skill incident-postmortem-oalansilva

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incident-postmortem
Source: https://github.com/oalansilva/crypto/tree/main/.codex/skills/reliability/incident-postmortem
Command: npx skills add https://github.com/oalansilva/crypto --skill incident-postmortem-oalansilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft a structured, blameless incident postmortem that clearly documents the timeline, root causes, and actionable improvements to prevent recurrence.

Core Features & Use Cases

RCA & Timeline: Compile incident events, evidence, and root cause analysis.
Actionable Outcomes: Define owners, due dates, and preventive actions.
Blameless & Systemic: Emphasize systemic failures over individual blame to improve reliability.
Use Case: After a production incident, generate a standard postmortem ready for sharing with stakeholders.

Quick Start

Draft a postmortem covering the incident, its impact, and the corrective actions taken.

Frequently Asked Questions about incident-postmortem

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

FAQPage Schema

How do I write a blameless incident postmortem for a software reliability incident?▼

A blameless incident postmortem emphasizes systemic failures over individual blame to improve reliability. It clearly documents the incident timeline, root causes, and actionable improvements to prevent recurrence across software systems.

What is the best way to structure an incident RCA with action items?▼

The best way to structure an incident RCA is to compile incident events, evidence, and change history into a chronological timeline, then define preventive action items with specific owners and due dates to ensure actionable outcomes.

Do I need incident logs and change history to draft a complete postmortem?▼

Yes, you need incident data, logs, and change history to accurately draft a complete postmortem. This input evidence is applied across reliability incidents to construct the timeline and perform the root cause analysis.

How do I create an incident postmortem ready to share with stakeholders?▼

To create a postmortem ready for stakeholders, draft a structured report covering the incident impact, its root cause analysis, and the corrective actions taken. The resulting document is formatted to be blameless and actionable.

Can I use a postmortem template to track preventive action items with owners and due dates?▼

Yes, a postmortem template defines actionable outcomes by assigning specific owners and due dates to preventive actions. This ensures accountability for systemic improvements following a production incident.