// Use after an incident is resolved — drafts a blameless postmortem from timeline notes, alerts, and chat threads.
| name | incident-postmortem |
| description | Use after an incident is resolved — drafts a blameless postmortem from timeline notes, alerts, and chat threads. |
| version | 0.1.0 |
| status | experimental |
| risk | low |
| tags | ["ops","writes-files"] |
incident-runbook instead)| Name | Type | Required | Notes |
|---|---|---|---|
timeline | text or paths | yes | Source notes, alert links, chat extracts |
severity | S0–S3 | yes | Severity at peak |
incident_id | string | yes | e.g. INC-2026-04-12-001 |
postmortem.md with: Summary, Impact, Timeline, Direct cause, Contributing factors, What went well, What didn't, Action items.
Use when capturing an architecture decision so it survives turnover — produces an ADR-NNNN.md from context, options considered, and the chosen path.
Use when reviewing a proposed REST or GraphQL API change before merge — checks contract clarity, backwards compatibility, errors, pagination, auth, and naming.
Use when first encountering a new dataset — produces a structured profile (schema, missingness, distributions, outliers, gotchas) before any analysis.
Use when opening a PR — produces a clean PR description (what / why / how to verify / risks) from a branch diff against base.
Use when planning the next sprint — turns ticket intake + team capacity into a planned sprint with explicit non-goals.
Use after a session to promote useful episodic notes from logs/episodic/ into distilled, dated entries in MEMORY.md and memory/semantic/.