postmortem-writing

Name: postmortem-writing
Availability: InStock
Author: timequity

Create blameless postmortems documenting root-cause analyses with structured markdown templates.

6|Updated Dec 7, 2025

Search Tags:#templates #documentation #learning #knowledge #postmortem #incident #blameless

Ready to run

npx skills add https://github.com/timequity/plugins --skill postmortem-writing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: postmortem-writing
Source: https://github.com/timequity/plugins/tree/main/craft-coder/postmortem-writing
Command: npx skills add https://github.com/timequity/plugins --skill postmortem-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to capture incident learnings without assigning blame. This Skill provides a structured, blameless template to document what happened, why it happened, impact, and actionable improvements.

Core Features & Use Cases

Structured template: Includes Incident Title, Date, Duration, Severity, Summary, Timeline, Root Cause, Impact, and Action Items.
Blameless culture: Emphasizes systems and processes, not people.
Knowledge sharing: Generates a reusable PRD-like document for team learning.

Quick Start

Use the template to draft a postmortem for an incident titled "Database latency spike" and fill in the timeline and root cause sections.

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

A blameless postmortem documents what happened, why it happened, and what to improve without assigning fault to individuals. Use a structured template covering incident title, timeline, root cause analysis, impact, and actionable follow-ups with assigned owners and due dates to capture lessons learned.

What should a postmortem template include?▼

Postmortem templates should include incident title, date, duration, severity level, summary, chronological timeline, root cause analysis, business and technical impact, and action items with clear ownership and deadlines. This structure ensures consistent documentation and knowledge sharing across teams.

Why focus on systems rather than people in incident reviews?▼

Blameless postmortems emphasize systemic and process failures instead of individual actions, which builds psychological safety and encourages honest incident reporting. This approach surfaces underlying weaknesses in architecture, monitoring, and runbooks that prevented earlier detection or mitigation.

Can I use postmortem documentation for team learning?▼

Yes. Postmortems generate reusable knowledge artifacts that document root causes, corrective actions, and lessons learned in a structured format. Teams can reference these documents to prevent similar incidents, improve runbooks, and share institutional knowledge across departments.

How do I ensure postmortem action items actually get completed?▼

Assign each action item to a specific owner with a concrete due date and track progress through follow-up. Linking actions to postmortem documents creates accountability and ensures corrective measures address identified root causes rather than symptoms.