postmortem-writing

Name: postmortem-writing
Availability: InStock
Author: Neuraz

Automate blameless postmortems with root cause analysis, timelines, and follow-ups.

Updated Apr 4, 2026

Search Tags:#timeline #postmortem #root-cause-analysis #blameless #action-items #lessons-learned #incident-review

Ready to run

npx skills add https://github.com/emilneuraz-ai/neuraz-web --skill postmortem-writing-emilneuraz-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: postmortem-writing
Source: https://github.com/emilneuraz-ai/neuraz-web/tree/main/.agents/skills/.agents/skills/postmortem-writing
Command: npx skills add https://github.com/emilneuraz-ai/neuraz-web --skill postmortem-writing-emilneuraz-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Blameless postmortems with root cause analysis, timelines, and action items help teams learn from incidents and improve response.

Core Features & Use Cases

Blameless culture focus on learning from incidents rather than assigning blame.
Structured templates to standardize executive summaries, timelines, root-cause analysis, lessons learned, and action items.
Cross-team application for incident reviews in software, operations, and security to ensure consistent documentation and sharing of learnings.

Quick Start

Draft a complete postmortem following the standard templates to document the incident timeline, root cause analysis, and 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 an incident?▼

A blameless postmortem is a blameless incident review document that captures the executive summary, timeline, root-cause analysis, lessons learned, and action items. It focuses on learning from incidents rather than assigning blame across software, operations, or security teams.

What should be included in incident review documentation?▼

Incident review documentation should include a structured executive summary, a detailed incident timeline, root-cause analysis, lessons learned, and concrete follow-up actions. Standardizing these sections ensures consistent documentation and sharing of learnings across teams.

How do I conduct a root-cause analysis for a software incident?▼

Conduct root-cause analysis for a software incident by mapping out the incident timeline and identifying contributing factors without assigning blame. Structured postmortem templates help standardize this analysis to drive learning and process improvements.

Can I use structured postmortem templates for security incident reviews?▼

Yes, you can use structured postmortem templates for security incident reviews. The templates apply across software, operations, and security teams to standardize documentation, capture timelines, and ensure consistent sharing of learnings from incidents.

What is the best way to track action items and lessons learned from incidents?▼

The best way to track action items and lessons learned is to document them as concrete follow-up actions within a blameless postmortem. Standardized templates capture these items to ensure learning-driven process improvements after incident reviews.