skills.rest
Hongyu-yu
Hongyu-yuCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

postmortem

Document incident timelines, root causes, and SMART corrective actions in structured postmortems.

16|Updated Dec 28, 2025
Search Tags:#learning#postmortem#root-cause-analysis#incident-management#blameless#5-whys#fishbone
One-click install
npx skills add https://github.com/Hongyu-yu/matsci-ai-skills --skill postmortem-hongyu-yu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/Hongyu-yu/matsci-ai-skills/tree/main/skills/postmortem
Command: npx skills add https://github.com/Hongyu-yu/matsci-ai-skills --skill postmortem-hongyu-yu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conduct blameless postmortems that transform failures into learning opportunities by documenting what happened, why it happened, impact quantification, root cause analysis, and actionable preventions with clear ownership.

Core Features & Use Cases

  • Structured templates for incident documentation, timelines, and action items.
  • Root-cause analysis techniques (5 Whys, fishbone) to uncover systemic issues.
  • SMART corrective actions with owners and deadlines to drive improvement.
  • Learning and knowledge sharing across teams through standardized formats.

Quick Start

Initiate a postmortem by creating a structured document using the provided template within 48 hours of incident resolution to capture timeline, impact, root cause, corrective actions, and lessons learned.

Frequently Asked Questions about postmortem

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

FAQPage Schema
How do I conduct a blameless postmortem after an incident?▼

To conduct a blameless postmortem, analyze failures and document learnings through structured templates that capture the incident timeline, quantify impact, and identify systemic issues without assigning individual blame.

What is the best way to perform root-cause analysis for an outage?▼

The best way to perform root-cause analysis for an outage is applying structured techniques like the 5 Whys or fishbone method within a postmortem template to uncover systemic issues driving the failure.

How do I create SMART corrective actions for incident management?▼

Create SMART corrective actions for incident management by assigning clear ownership and deadlines to specific, measurable prevention steps identified during root-cause analysis, ensuring accountable tracking workflows.

When do I need to document a postmortem for a near-miss?▼

You need to document a postmortem for a near-miss within 48 hours of incident resolution to transform the event into a structured learning opportunity with actionable preventions and clear ownership.

Can I use this postmortem process for product and operations teams?▼

Yes, you can use this postmortem process for product and operations teams, as the structured root-cause analysis and corrective action tracking workflows are applicable across engineering, product, and operational after-action reviews.

Related Skills

Explore More Software Engineering Skills→
tclemtclem
11

incident-postmortem

Collect incident data, logs, and metrics into structured postmortem reports.

Community
Intermediate
edwardmonteiroedwardmonteiro

optimization.postmortem

Generate standardized postmortem documents with root-cause analysis and corrective actions.

Community
Basic
1479089714790897
7

kwp-engineering-incident-response

Manage incident response lifecycle with triage, status updates, and postmortem generation.

Community
Advanced
serac-labsserac-labs
77

debugging-mutations

Inspect post-action mutations and logs in ServiceNow to verify changes.

Official
Advanced