postmortem-writing

Create structured postmortem documents with root cause analysis, timelines, and action items.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/PriyanshKuniyal/gemini-cli-resources --skill postmortem-writing-priyanshkuniyal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postmortem-writing
Source: https://github.com/PriyanshKuniyal/gemini-cli-resources/tree/main/extensions/claude-code-workflows/plugins/incident-response/skills/postmortem-writing
Command: npx skills add https://github.com/PriyanshKuniyal/gemini-cli-resources --skill postmortem-writing-priyanshkuniyal

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill empowers incident responders to write comprehensive and blameless postmortems, fostering a culture of continuous improvement.

Core Features & Use Cases

  • Root Cause Analysis: Facilitates a structured approach to identifying the root cause of incidents.
  • Timeline Construction: Guides the creation of detailed incident timelines.
  • Action Item Generation: Supports the creation of actionable follow-up items to prevent recurrence.
  • Use Case: Ideal for incident review teams seeking to document and analyze major service disruptions in a clear, systematic manner.

Quick Start

Generate a postmortem document for the recent 'database outage' incident.

Frequently Asked Questions about postmortem-writing

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

FAQPage Schema
How do I write a blameless postmortem for a major service disruption?

Root cause analysis for incident response identifies the underlying systemic factors of a failure. This skill structures your investigation into a blameless postmortem document, guiding timeline creation and action item generation to support continuous improvement.

What is the best way to document an incident timeline for root cause analysis?

Documenting an incident timeline requires chronologically capturing detection, mitigation, and resolution events. This skill facilitates structured timeline construction alongside root cause analysis to ensure a comprehensive postmortem review of the disruption.

How do I generate action items to prevent incident recurrence after a database outage?

Generating action items requires translating root cause findings into specific, accountable tasks. This postmortem skill supports the creation of actionable follow-up items from your incident analysis, helping mitigate the risk of a similar database outage.

When do I need a structured postmortem document for incident response?

You need a structured postmortem document when analyzing major service disruptions to ensure continuous improvement. It provides a blameless framework for root cause analysis and action item tracking, making it ideal for incident review teams.

Does blameless postmortem writing work for small development teams or only large-scale operations?

Blameless postmortem writing works for incident review teams of any scale seeking to document service disruptions. The structured analysis, timeline creation, and action item generation support organizational learning regardless of team size.