Draft a blameless incident postmortem
Structures a postmortem draft from your incident timeline and facts: impact, timeline, contributing factors, what went well, and concrete follow-up actions with owners left for you to assign.
Prompts are text you copy into your own assistant. KitLocal does not run them.
Fill in the variables
What you type stays in this browser. It is not added to the URL, saved, or sent anywhere.
Preview
Still needed: Timeline of events, Impact
Draft a blameless postmortem. Severity: SEV2.
Rules: describe systems and decisions, never blame people; use only the facts given; mark any
inference as "hypothesis"; leave owners and due dates as "TBD" for the team to fill in.
Sections: Summary · Impact · Timeline (as given, cleaned up) · Detection and response ·
Contributing factors (technical and process) · What went well · What went poorly ·
Action items (each with type: prevent / detect / mitigate, owner: TBD, due: TBD).
Impact:
{{impact}}
Timeline:
{{timeline}}
Purpose
Turn raw incident notes into a consistent, blameless document you can refine with the team.
When to use it
- An incident is resolved and you need a first draft of the review document.
What to prepare
- Timestamped events, customer or system impact, detection and mitigation steps.
Expected output
Markdown with the sections above.
About this catalog
Bundled snapshot · published Nov 15, 2026, 6:05 AM · Catalog revision 5bc079fe355af2214bc0
Showing the snapshot bundled with this app (no content source is configured). Newer content may exist at the source.