Skip to content
KRPUS
Sign up

From Slack chaos to a blameless postmortem.

Severity matrix, services, an incident log and timeline, comms templates, postmortems and the actions that follow them. You run the incident and make the calls; the agent keeps the paperwork.

  1. 1 · @maraPastes the channel exportCheckout failed for 46 minutes on Monday morning. After the rollback, @mara hands the incident channel to Claude.
  2. 2 · agent/incident-scribeBuilds the timeline, drafts the postmortemWrites the INC-0042 timeline into incidents/INC-0042 and drafts the postmortem from the template: summary, impact, contributing factors.
  3. 3 · agent/incident-scribeProposes actions, sets no causeSuggests AI-101 to AI-104 with owners and due dates. Cause category and severity are the commander’s call, so it mentions @mara.
  4. 4 · @maraThe incident commander signs offKeeps SEV2, sets the cause to config and marks the postmortem reviewed. The agent chases the actions until they are done.
The postmortem of INC-0042 in the Incident Response & Postmortems bundle: SEV2, checkout-api, 46 minutes of failed checkouts after a connection pool changeThe postmortem of INC-0042 in the Incident Response & Postmortems bundle: SEV2, checkout-api, 46 minutes of failed checkouts after a connection pool change
Next case · Security auditAudit evidence that stays current all year.

Give your agents a memory your team can read.

Free to start, no card needed. For a demo or running it in your own AWS account, write to us.

Start freeGet in touch