postmortem-writing

Generate blameless postmortem documents with templates, timelines, and action items.

70|42|Updated Mar 27, 2026

Search Tags:#timeline #postmortem #root-cause-analysis #incident-response #action-items #blameless-culture

Ready to run

npx skills add https://github.com/tranhieutt/software_development_department --skill postmortem-writing-tranhieutt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: postmortem-writing
Source: https://github.com/tranhieutt/software_development_department/tree/main/.claude/skills/postmortem-writing
Command: npx skills add https://github.com/tranhieutt/software_development_department --skill postmortem-writing-tranhieutt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Producing structured, blameless postmortems is difficult without a clear process, and this Skill removes uncertainty by guiding you through incident timelines, root causes, and concrete follow-up actions so teams can learn instead of blaming.

Core Features & Use Cases

Guided Templates: Offers Standard, 5 Whys, and Quick formats to capture executive summaries, timelines, RCA, detection gaps, and action items tailored to the incident severity.
Facilitation Support: Provides meeting structure, anti-patterns, and best practices so reviewers stay blameless, document decisions, and assign owners during postmortem meetings.
Organizational Learning: Encourages documenting impacts, lessons, and systemic improvements, and points to resources like the implementation playbook for detailed examples.

Quick Start

Ask the skill to draft a blameless postmortem outline for the latest outage using the Standard template so you can review the timeline, detection, response, and action items.

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 production incident?▼

To write a blameless postmortem, use guided templates to capture the incident timeline, root causes, detection gaps, and action items without assigning blame. This process focuses on systemic improvements and organizational learning rather than individual fault.

What is the 5 Whys root-cause-analysis method for incident response?▼

The 5 Whys root-cause-analysis method is an incident response technique that repeatedly asks why an outage occurred to uncover fundamental systemic issues. It is offered as a specific postmortem template alongside Standard and Quick formats.

How do I facilitate a post-incident meeting to review an outage timeline?▼

Facilitate a post-incident meeting by applying provided meeting structures, anti-patterns, and best practices to review the outage timeline blamelessly. This ensures reviewers document decisions, assess detection and response, and assign action item owners.

What's the best way to document action items after root-cause analysis?▼

The best way to document action items after root-cause-analysis is to prioritize tickets and assign them to specific owners with deadlines. This ensures accountability and tracks systemic improvements derived from the incident postmortem.

Can I use a quick postmortem template for low-severity incidents?▼

Yes, you can use a Quick postmortem template for low-severity incidents. The Skill offers Standard, 5 Whys, and Quick formats so you can tailor executive summaries, timelines, and action items to match the specific incident severity.