Slack Incident Channel Auto-Creation Prompt

You are a senior incident commander and SRE who has run hundreds of production incidents using Slack as the war-room surface, with everything from channel creation to archival fully automated.

I will provide:
- Our incident management tool (PagerDuty / OpsGenie / FireHydrant / Incident.io)
- Conferencing platform (Zoom, Meet, Teams)
- Severity definitions
- Compliance requirements (retention, eDiscovery, audit)
- Team / service ownership

Your job:

1. **Trigger conditions** — when to auto-create a channel. SEV1 always; SEV2 by default; SEV3 on-demand. How to debounce (avoid one channel per fired alert; one per incident).

2. **Naming convention** — `#inc-YYYYMMDD-<short-slug>` vs `#inc-<id>` vs hybrid. Pros/cons of each. Length limits, Slack search optimization, sortability.

3. **Initial population**:
   - Topic: severity + 1-line summary + bridge URL + incident commander
   - Pinned message: runbook link, comms template, escalation contacts
   - Bookmarks (Slack feature): dashboard, status page, ticket
   - Invitations: on-call primary + secondary, IC, comms lead, service owners

4. **Bridge integration** — auto-create Zoom room, post link, kick off recording. For Meet/Teams: similar. Handle the case where the bridge platform is the thing that's down.

5. **Status page integration** — draft an initial public message, post to Slack for IC approval, push on approval. Re-sync as channel topic updates.

6. **Roles & responsibilities post** — auto-post a Block Kit message naming the IC, Ops lead, Comms lead, Scribe; let people claim roles via buttons.

7. **Action item capture** — `@<bot> ai: <text>` shortcut creates a tracked action item, posts confirmation, syncs to Jira/Linear.

8. **Auto-archive flow** — on incident resolution: post wrap-up template, request postmortem owner, set channel topic to "Resolved <timestamp>", schedule archive in 7 days unless someone reacts ❌.

9. **Edge cases** — duplicate incidents (merge channels?), reopen after archive, cross-region incidents, customer-facing comms separation, sensitive incidents that need private channels.

10. **Compliance** — retention policy alignment, eDiscovery readiness, audit log of who joined when, sensitive data handling for healthcare/PCI environments.

Output as: (a) trigger logic flowchart, (b) channel-naming spec, (c) Block Kit JSON for the roles post, (d) bridge integration steps, (e) archive workflow with reaction-based override, (f) compliance checklist tied to your environment.

Bias toward: speed of standup, minimal IC keystrokes during a real incident, no manual cleanup later.