postmortem-writing

Draft blameless incident reports with root causes, timelines, and follow-ups.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/ArogyaReddy/https-github.com-wshobson-agents --skill postmortem-writing-arogyareddy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postmortem-writing
Source: https://github.com/ArogyaReddy/https-github.com-wshobson-agents/tree/main/plugins/incident-response/skills/postmortem-writing
Command: npx skills add https://github.com/ArogyaReddy/https-github.com-wshobson-agents --skill postmortem-writing-arogyareddy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Postmortem-writing solves the challenge of capturing detailed incident learnings in a structured, blameless format that spans root-cause analysis, timelines, and actionable follow-ups.

Core Features & Use Cases

  • Structured templates for root-cause analysis, timeline construction, and action-item tracking
  • Guided workflows to draft, review, and socialize postmortems across teams
  • Use Case: Draft postmortems for incident reviews to improve incident response processes and organizational learning

Quick Start

Draft a blameless postmortem for a recent incident by outlining the timeline, identifying root causes, and listing concrete follow-up actions.

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 after a major incident?

A blameless postmortem requires documenting the incident timeline, performing root-cause analysis, and listing action items without assigning blame. This skill provides structured templates to guide teams through collaborative authoring and clear follow-up tracking.

What is the best way to structure root-cause analysis for incident reviews?

Root-cause analysis for incident reviews should be structured using templated formats that capture the timeline, identify underlying causes, and define actionable follow-ups. This skill drives a structured workflow to ensure comprehensive organizational learning.

How do I track action items from an incident review so they actually get done?

Tracking action items from an incident review involves listing concrete follow-up actions within a structured postmortem document. This skill enables teams to draft, review, and socialize reports to ensure accountability and improve incident response processes.

Can I use a template-driven workflow for collaborative postmortem authoring across teams?

Yes, template-driven workflows support collaborative authoring across teams by providing structured formats for root-cause analysis and timelines. This skill enables teams to draft, review, and socialize incident reports effectively.

When should I use a structured postmortem format instead of a simple incident summary?

A structured postmortem format is needed when you require comprehensive root-cause analysis, a detailed timeline, and actionable follow-up items. This skill satisfies those requirements for incident reviews spanning engineering and operations.

Does this postmortem-writing skill require any specific external tools or integrations?

No, this postmortem-writing skill operates independently without external dependencies. It provides structured templates and guided workflows to help teams document incidents, identify root causes, and track follow-up actions.