nw-post-mortem-framework

Structure incident retrospectives with timelines, root-cause analysis, and action items.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/StudentCristian/nWave-github --skill nw-post-mortem-framework
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nw-post-mortem-framework
Source: https://github.com/StudentCristian/nWave-github/tree/main/.github/skills/nw-post-mortem-framework
Command: npx skills add https://github.com/StudentCristian/nWave-github --skill nw-post-mortem-framework

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Blameless post-mortem framework for incident retrospectives provides a structured approach to capture timelines, findings, and actionable learning without blaming individuals, improving reliability and organizational learning.

Core Features & Use Cases

  • Structured Post-Mortem Template: standard sections for timeline, root cause analysis, and action items.
  • Evidence-based Evaluation: ties findings to logs, metrics, and documented actions.
  • Learning & Improvement: converts findings into concrete actions and runbooks.
  • Use Case: for any incident from runtime outages to security incidents, enabling rapid reconstruction and learning.

Quick Start

Begin a guided post-mortem session using the framework and fill in the template with incident details.

Frequently Asked Questions about nw-post-mortem-framework

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

FAQPage Schema
What is a blameless post-mortem and how does it improve incident management?▼

A blameless post-mortem is a structured incident retrospective focusing on root-cause analysis and timeline reconstruction without attributing individual blame. This approach improves operational reliability by converting evidence-based findings into actionable learning and runbooks.

How do I write an incident post-mortem for a runtime outage?▼

To write an incident post-mortem, use a structured template to document the timeline, perform root-cause analysis, and list action items. Tie findings to logs and metrics to ensure evidence-based evaluation and drive operational improvement.

Can I use this post-mortem framework for security incidents across varying severities?▼

Yes, this post-mortem framework applies to engineering and operations teams for any incident, from runtime outages to security incidents. It supports varying severities by providing a reproducible template for timeline reconstruction and organizational learning.

What is the best way to ensure post-mortem findings lead to operational improvement?▼

The best way to drive operational improvement is to use a post-mortem template that converts evidence-based findings into concrete action items and runbooks. This ensures structured documentation and blameless learning across the engineering team.

Does incident timeline reconstruction require specific log formats or metrics?▼

Incident timeline reconstruction relies on evidence-based evaluation, meaning findings must be tied to available logs, metrics, and documented actions. The framework standardizes how this evidence is captured within the reproducible post-mortem document structure.

Why do blameless retrospectives focus on organizational learning instead of individual blame?▼

Blameless retrospectives focus on organizational learning because shifting focus from individual blame to evidence-based root-cause analysis reveals systemic issues. This approach improves reliability by creating actionable items and runbooks from structured incident findings.