incident-postmortem

Generate structured post-mortem documents for P1 and P2 production incidents.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/s3nex-com/sdlc-skills-library --skill incident-postmortem-s3nex-com
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-postmortem
Source: https://github.com/s3nex-com/sdlc-skills-library/tree/main/skills/phase3/incident-postmortem
Command: npx skills add https://github.com/s3nex-com/sdlc-skills-library --skill incident-postmortem-s3nex-com

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-incident learning is often delayed and inconsistent; this skill provides a structured, blameless process to analyze incidents, capture evidence, and drive targeted improvements.

Core Features & Use Cases

  • Structured post-mortem templates that guide severity, timeline, root cause analysis, action items, and lessons learned.
  • Facilitates blameless culture and accountability with clear owners and due dates.
  • Use Case: After a P1 incident, generate a formal post-mortem to share findings with stakeholders and track improvement actions.

Quick Start

Draft a complete post-mortem document for a recent incident including severity, timeline, root cause, and action items.

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 post-mortem after a production incident?

A blameless post-mortem analyzes production incidents by focusing on systemic issues rather than individual mistakes. It uses structured templates to document timelines, root causes, and action items to drive improvements across teams.

What is included in a root-cause analysis for a P1 incident?

Root-cause analysis for a P1 incident includes a structured timeline, identification of the underlying cause, documentation of what went well or poorly, and tracked action items with clear owners and due dates.

How do I track action items and lessons learned from an incident response?

You track action items and lessons learned by generating a formal post-mortem document that assigns clear owners and due dates to follow-up items, ensuring accountability and driving targeted improvements after incident response.

Can I use this post-mortem template for both P1 and P2 incidents?

Yes, the post-mortem template is applicable to both P1 and P2 incidents. It provides a structured framework to capture impact, timeline, root cause, and lessons learned regardless of the severity level.

What is the best way to document incident timelines for stakeholders?

The best way to document incident timelines for stakeholders is using a structured post-mortem framework. It records chronological events, captures impact, and formalizes lessons learned to share findings and track improvement actions.