skills.rest
JayRHa
JayRHaCOMMUNITY
Explore all skills by this author →
Website𝕏@jannik_reinhardGitHub

incident-postmortem

Generate blameless postmortems with timelines, root causes, and owner-dated action items.

3|2|Updated Jun 9, 2026
Search Tags:#timeline#postmortem#root-cause-analysis#incident-management#blameless#action-items
One-click install
npx skills add https://github.com/JayRHa/AgentSkills --skill incident-postmortem-jayrha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: incident-postmortem
Source: https://github.com/JayRHa/AgentSkills/tree/main/incident-postmortem
Command: npx skills add https://github.com/JayRHa/AgentSkills --skill incident-postmortem-jayrha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps teams generate blameless incident postmortems by reconstructing precise timelines, identifying root causes and contributing factors, and producing tracked, owned action items after a service disruption.

Core Features & Use Cases

  • Reconstruct timelines from incident data to build a clear narrative for stakeholders.
  • Identify root causes and contributing factors using established blameless techniques and templates.
  • Generate a structured postmortem document with owner-dated action items and follow-ups.

Quick Start

Run through the templates and references to generate a complete postmortem for a resolved outage.

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 postmortem after a service outage?▼

To generate a blameless postmortem, apply established templates to reconstruct the incident timeline, identify root causes, and produce owner-dated action items. This enforces blameless language and structured, auditable tracking.

What is a blameless postmortem and why is it needed for incident management?▼

A blameless postmortem is a structured document generated after a resolved incident to reconstruct timelines and identify root causes without assigning individual blame. It is needed to track auditable action items and prevent recurrence.

How do I reconstruct an incident timeline for root cause analysis?▼

You reconstruct an incident timeline by processing resolved incident data through structured templates to build a clear narrative for stakeholders. This timeline is then used to identify root causes and contributing factors accurately.

Can I generate tracked action items from a root cause analysis?▼

Yes, you can generate structured, owner-dated action items directly from the root cause analysis. The process ensures that every follow-up is tracked, owned, and auditable within the final postmortem document.

Does this postmortem process work for complex incidents with multiple contributing factors?▼

Yes, the postmortem process is designed to identify multiple contributing factors using established blameless techniques. It reconstructs precise timelines to ensure all systemic issues are documented and addressed with structured action items.

Related Skills

Explore More Software Engineering Skills→
yongwoonyongwoon
8

ywc-incident-postmortem

Generate structured incident postmortems with timeline reconstruction and 5 Whys analysis.

Community
Advanced
ramybarsoumramybarsoum

incident-postmortem

Convert raw incident notes into structured postmortem documents with RCA and action items.

Community
Intermediate
carson-sweetcarson-sweet
6

postmortem

Creates post-mortem documentation from git logs and generates issue tracking items.

Community
Advanced
tianjianjiangtianjianjiang
1

smith-postmortem

Guide structured, blameless incident postmortems with root cause analysis and action-item tracking.

Community
Advanced