What's your current incident workflow? Building an incident tracker for Slack

Working on an incident management bot that lives in Slack and uses AI to write postmortems from your actual debugging conversations.

The idea: one /incident start command creates a war room, pages on-call, records everything, and when you resolve, AI generates a postmortem analyzing what was said (not just formal status updates).

The flow for creating incidents:

• /incident start <sev> <title> - Creates a channel to keep track of the incident and pages the oncall user if there's one

• /incident status <update> - Creates an update event on the incident with a timestamp

• /incident severity <sev> - Updates the severity of the incident

• /incident resolve - Resolves the incident with a timestamp

• /incident postmortem - Creates an AI generated postmortem gathering context from the status and conversation in the channel

It also includes an /oncall command to manage on-call users and auto-rotation and a /page command to page on-call users

Curious before we launch:

• Do you actually write postmortems today? What's the friction?

• Would you trust AI to draft them?

• What integrations are non-negotiable? (PagerDuty ✅, Jira ✅, Linear, Notion, Github Issues, ClickUp?)

Would love all of the feedback available and happy to share what we learn. 🚀

You can check out all of the commands and information at https://incidentops.io