Incident Postmortem
Scaffolds a structured postmortem with incident summary, timeline reconstruction, root cause analysis using the 5 Whys method, impact assessment, and lessons learned. Optionally includes a follow-up action tracker. Designed for SRE and engineering teams conducting blameless postmortems after production incidents.
| Name | incident-postmortem |
| Version | 0.1.0 |
| Category | operations |
| License | Apache-2.0 |
| Persona | operations |
| Tags | postmortem, incident, root-cause, timeline, action-items, sre |
| Source | templates/incident-postmortem |
Render it
Three front doors, one catalog. Pick whichever suits the caller.
# CLI
npx @nanohype/sdk render incident-postmortem --out ./my-app
# SDK
import { LocalSource, renderTemplate } from "@nanohype/sdk";
const result = await renderTemplate(source, "incident-postmortem", variables);
# MCP — from an agent
get_template({ name: "incident-postmortem" })Variables
Required
ProjectNamestring- Kebab-case project name used as the document directory Must be lowercase kebab-case starting with a letter.
ServiceNamestring- Human-readable service name for document titles
Optional
IncludeFollowUpbool — defaults totrue- Include a follow-up action tracker
What it produces
3 files. Placeholder names such as __APP_NAME__ are what the renderer substitutes into.
postmortem/follow-up-tracker.yaml
postmortem/template.md
postmortem/timeline.yamlComposes with
- Pairs with
runbook - Pairs with
compliance-checklist - Pairs with
monitoring-stack - Nests inside
monorepo