incident-postmortem

Compile incident timelines, root-cause chains, and owned prevention actions.

7|Updated Feb 14, 2026

Search Tags:#timeline #learning #reliability #postmortem #root-cause-analysis #incident #corrective-actions

Ready to run

npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill incident-postmortem-kentoshimizu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incident-postmortem
Source: https://github.com/KentoShimizu/sw-agent-skills/tree/main/skills/incident-postmortem
Command: npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill incident-postmortem-kentoshimizu

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Incident postmortem workflow for evidence-backed root cause analysis and systemic prevention actions. Use after incident stabilization when teams need timeline, root-cause chain, contributing factors, and owned prevention actions; do not use for active incident command and real-time mitigation.

Core Features & Use Cases

Evidence-backed analysis: Build a structured timeline, identify root causes, and capture contributing factors with traceable evidence.
Actionable prevention: Create owners, due dates, and verification for corrective actions to reduce recurrence.
Documentation templates: Use standardized postmortem report and trackers to document lessons learned and follow-up work.

Quick Start

Run incident postmortem workflow after incident stabilization to generate an evidence-backed report and an action plan.

Frequently Asked Questions about incident-postmortem

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

FAQPage Schema

How do I write an incident postmortem report with root cause analysis?▼

An incident postmortem report documents the timeline, identifies root causes, and captures contributing factors with traceable evidence. It guides teams through structured documentation to ensure prevention actions are assigned and verifiable.

What's the best way to assign owners and due dates for corrective actions after an incident?▼

Assign owners and due dates for corrective actions by creating a prevention tracker with verifiable completion checks. This ensures accountability and reduces incident recurrence by formalizing remediation tasks with clear deadlines.

When should I start the incident postmortem process?▼

Start the incident postmortem process after incident stabilization when active mitigation is complete. It is designed for post-incident reviews to document timelines and root causes, not for real-time incident command.

How do I trace contributing factors to evidence during a root-cause analysis?▼

Trace contributing factors by mapping them to specific timeline artifacts and evidence captured during the incident. This evidence-backed analysis ensures identified causes are grounded in documented facts rather than assumptions.

Can I use this postmortem workflow for active incident command and real-time mitigation?▼

No, this postmortem workflow is strictly for post-incident reviews after stabilization. It focuses on compiling timelines and prevention actions, and does not support active incident command or real-time mitigation.