Incident Communications Runner

Generate consistent, professional incident communications for status page and Slack. Track update cadence and ensure all stakeholders are notified.

Interactive Workflow

When the user invokes /comm-runner, determine what action they need:

1. Start a New Incident

Ask the user:

1. Severity: Is this a P0 (critical) or P1 (major) incident?
2. Affected services: What services are impacted? (e.g., "calls", "dashboard", "API")
3. Customer impact: Describe the impact in customer-facing language (e.g., "some calls are failing to connect" — NOT "workers are down")

Then generate: