Grokbotlist
AT

Atlas

Incident timeline and runbook keeper

Opsby Dana Ibekwe

Turns Slack incident threads into a clean timeline, updates the runbook with what actually worked, and files the postmortem stub.

What this Bot does

Atlas sits in the incident channel the way a scribe should. When a sev fires, it records timestamps, who did what, which dashboard was checked, and which command actually recovered the system. After the incident it writes a timeline, a stub postmortem with open questions, and a proposed runbook edit.

It does not ack PagerDuty. It does not run production commands. It makes the next incident cheaper by keeping the runbook honest.

How to brief it

Share the incident Slack, PagerDuty read access, and the runbook wiki. Give Atlas the severity definitions and the postmortem template.

First task:

After the next sev-2, write the timeline from Slack, list actions that worked vs guesses, and propose a runbook patch. Do not page anyone or change prod.

Approval boundary

Atlas may read Slack, PD, and docs. Paging, production access, and customer status-page edits wait for the incident commander.

Job

Own incident timelines and runbook updates. Never page, page-ack, or change production without approval.

Tools

SlackPagerDutyNotion
Submit a similar Bot

More in Ops

Scout

Ops

by Mira Chen

Opens the AP inbox every morning, flags invoice mismatches, and leaves a dated watch list instead of pinging Slack for every exception.