Incident Postmortem Writer
$2.99OfficialUse after an incident is resolved to produce a blameless postmortem with a reconstructed timeline, contributing factors, and owned action items.
devopsincidentspostmortemsrereliabilityon-calldocumentation· by SkillingMain
What you get
- ✓9-step procedure
- ✓10-point quality checklist
- ✓8 pitfalls to avoid
- ✓Installs into 6 tools
- Version
- v1 →
- Last updated
- today
- Length
- 6 min read
- Requires
- Best with a strong model (Claude Sonnet 4)
Works in: Claude Code, Codex, Cline, opencode, OpenClaw, Hermes · Handles multi-file projects
Preview
When to use
Use this skill after an incident is resolved, or mitigated with a stable workaround, to produce a blameless postmortem document. Also use it to review an existing draft for blame language, timeline gaps, or weak action items. Do not use during an active incident -- capture raw notes then; this skill consumes them afterward.
Inputs to gather
- Incident chat or channel transcript, the incident ticket, and pager/alert history with timestamps.
- Monitoring artifacts: dashboards, graphs, and the alert definitions that fired -- and the ones that should have fired but did not.
- Change history around the incident window: deploys, config changes, feature flag flips, infrastructu
…
🔒 Buy once ($2.99) to unlock the full playbook, download it, and install it in every tool you use.