How do I install the Nw Post Mortem Framework skill?

Run npx skillmds add thedixitjain/nw-post-mortem-framework in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Nw Post Mortem Framework safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Nw Post Mortem Framework?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Nw Post Mortem Framework free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Nw Post Mortem Framework?

thedixitjain (@thedixitjain) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Nw Post Mortem Framework by thedixitjain

Name: Nw Post Mortem Framework
Rating: 4.2 (5 reviews)
Author: thedixitjain

File contents

Post-Mortem Framework

Principles

Blameless: focus on systems/processes, not individuals. People make reasonable decisions given available info.
Evidence-based: every finding backed by logs, metrics, or documented actions
Action-oriented: every finding produces concrete, assigned action item
Learning-focused: capture what worked alongside what failed

Post-Mortem Document Structure

# Post-Mortem: [Incident Title]

**Date**: [incident date]
**Duration**: [start to resolution]
**Severity**: [P0-P3]
**Author**: [analyst]

## Summary
[2-3 sentence overview: what happened, impact, resolution]

## Timeline
| Time | Event | Source |
|------|-------|--------|
| HH:MM | [event] | [log/metric/report] |

## Impact
- Users affected: [number/percentage]
- Duration of impact: [time]
- Business impact: [quantified if possible]
- Systems affected: [list]

## Root Cause Analysis
[5 Whys analysis with evidence at each level]

## Detection and Response
- Time to detect: [duration] -- [how detected]
- Time to respond: [duration] -- [first action]
- Time to mitigate: [duration] -- [mitigation applied]
- Time to resolve: [duration] -- [permanent fix]

## What Went Well
- [positive observations about detection, response, recovery]

## What Could Be Improved
- [areas where detection, response, recovery fell short]

## Action Items
| ID | Action | Owner | Priority | Due Date |
|----|--------|-------|----------|----------|
| 1 | [specific action] | [team/person] | [P0-P3] | [date] |

## Lessons Learned
- [key takeaways for the organization]

Incident Timeline Reconstruction

Sources

Monitoring alerts/dashboards (timestamps) | 2. Deployment logs/CI-CD records
Communication channels (Slack, email, incident) | 4. VCS (commits, merges, deploys) | 5. User reports/support tickets

Quality Checks

Events chronological with verified timestamps | gaps >5 min noted/explained | decision points identified with available info | causal relationships noted

Response Effectiveness Evaluation

Detection

Detected by monitoring or users? | Duration onset-to-detection? | Existing alerts relevant? Missing?

Escalation

Right team at right time? | Procedures followed? | Communication clear to stakeholders?

Resolution

Mitigation effective? | Rollback considered/viable? | Duration mitigation-to-permanent-fix?

Organizational Learning

Knowledge Capture

Document root causes as reusable patterns | update runbooks | share in retrospectives

Process Improvements

Update monitoring/alerting per detection gaps | revise deployment per rollback effectiveness | strengthen testing for failure scenario

Action Item Tracking

Every item has owner + due date | track in standups/sprint reviews | verify effectiveness post-deployment

Source: nWave-ai/nWave → nWave/skills/nw-post-mortem-framework/SKILL.md

Also appears in: nWave-ai/nWave/plugins/nw/skills/nw-post-mortem-framework/SKILL.md

---name: nw-post-mortem-frameworkdescription: Blameless post-mortem structure, incident timeline reconstruction, response evaluation, and organizational learning---# Post-Mortem Framework## Principles- **Blameless**: focus on systems/processes, not individuals. People make reasonable decisions given available info.- **Evidence-based**: every finding backed by logs, metrics, or documented actions- **Action-oriented**: every finding produces concrete, assigned action item- **Learning-focused**: capture what worked alongside what failed## Post-Mortem Document Structure```markdown# Post-Mortem: [Incident Title]**Date**: [incident date]**Duration**: [start to resolution]**Severity**: [P0-P3]**Author**: [analyst]## Summary[2-3 sentence overview: what happened, impact, resolution]## Timeline| Time | Event | Source ||------|-------|--------|| HH:MM | [event] | [log/metric/report] |## Impact- Users affected: [number/percentage]- Duration of impact: [time]- Business impact: [quantified if possible]- Systems affected: [list]## Root Cause Analysis[5 Whys analysis with evidence at each level]## Detection and Response- Time to detect: [duration] -- [how detected]- Time to respond: [duration] -- [first action]- Time to mitigate: [duration] -- [mitigation applied]- Time to resolve: [duration] -- [permanent fix]## What Went Well- [positive observations about detection, response, recovery]## What Could Be Improved- [areas where detection, response, recovery fell short]## Action Items| ID | Action | Owner | Priority | Due Date ||----|--------|-------|----------|----------|| 1 | [specific action] | [team/person] | [P0-P3] | [date] |## Lessons Learned- [key takeaways for the organization]```## Incident Timeline Reconstruction### Sources1. Monitoring alerts/dashboards (timestamps) | 2. Deployment logs/CI-CD records3. Communication channels (Slack, email, incident) | 4. VCS (commits, merges, deploys) | 5. User reports/support tickets### Quality ChecksEvents chronological with verified timestamps | gaps >5 min noted/explained | decision points identified with available info | causal relationships noted## Response Effectiveness Evaluation### DetectionDetected by monitoring or users? | Duration onset-to-detection? | Existing alerts relevant? Missing?### EscalationRight team at right time? | Procedures followed? | Communication clear to stakeholders?### ResolutionMitigation effective? | Rollback considered/viable? | Duration mitigation-to-permanent-fix?## Organizational Learning### Knowledge CaptureDocument root causes as reusable patterns | update runbooks | share in retrospectives### Process ImprovementsUpdate monitoring/alerting per detection gaps | revise deployment per rollback effectiveness | strengthen testing for failure scenario### Action Item TrackingEvery item has owner + due date | track in standups/sprint reviews | verify effectiveness post-deployment---**Source:** [`nWave-ai/nWave`](https://github.com/nWave-ai/nWave) → `nWave/skills/nw-post-mortem-framework/SKILL.md`**Also appears in:** `nWave-ai/nWave/plugins/nw/skills/nw-post-mortem-framework/SKILL.md`

Frequently asked questions