nw-post-mortem-framework

Organize blameless post-mortems with structured incident templates.

Updated Mar 18, 2024
One-click install
npx skills add https://github.com/v1bh0r/precise-ledger-pro --skill nw-post-mortem-framework-v1bh0r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nw-post-mortem-framework
Source: https://github.com/v1bh0r/precise-ledger-pro/tree/main/nWave/skills/nw-post-mortem-framework
Command: npx skills add https://github.com/v1bh0r/precise-ledger-pro --skill nw-post-mortem-framework-v1bh0r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, blameless approach to documenting incidents, timelines, root causes, and learning to prevent recurrence.

Core Features & Use Cases

  • Structured incident templates for timeline reconstruction, evidence capture, and action-item tracking.
  • Consistent documentation across teams to enable audits, knowledge sharing, and process improvements.
  • Use Case: After a production incident, teams reconstruct the sequence of events, identify improvements, assign owners, and track changes over time.

Quick Start

Begin by documenting your incident using the provided template and fill in the title, date, severity, timeline, root cause, and actions.

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 help with incident management?

A blameless post-mortem is a structured incident management process that reconstructs event timelines and identifies root causes without assigning individual fault, enabling teams to document evidence, track action items, and prevent incident recurrence.

How do I document an incident timeline for root-cause analysis?

To document an incident timeline for root-cause analysis, use a standardized post-mortem template to record the sequence of events, capture supporting evidence, and log corrective actions, ensuring consistent organizational learning across software teams.

What is the best way to track action items after a production incident?

The best way to track action items after a production incident is using a structured post-mortem framework that assigns specific owners to each corrective measure, ensuring follow-through on lessons learned and driving continuous process improvements over time.

Can I use a standardized post-mortem template across different software teams?

Yes, you can use a standardized post-mortem template across different software teams to ensure consistent documentation of incident severity, timelines, and root causes, which enables reliable audits, knowledge sharing, and streamlined organizational learning.

What sections should be included in a post-mortem report for organizational learning?

A post-mortem report for organizational learning should include structured sections for the incident timeline, root cause analysis, captured evidence, and lessons learned, ensuring that actionable improvements are documented and assigned for tracking.