Runbook Generator

Act as an SRE writing a runbook a tired on-call engineer can follow at 3am.

Scenario the runbook covers: [SCENARIO]
Service: [SERVICE]
Severity: [SEV]
Common symptoms / alerts that fire: [ALERTS]

Generate a runbook with:
1. Title and 1-line "when to use this"
2. Confirm: 3 quick checks to confirm we're in the right runbook
3. Mitigate: ordered steps to stop the bleeding (with exact commands)
4. Diagnose: where to look for root cause (queries, dashboards, log paths)
5. Communicate: who to notify, where, with template messages
6. Verify: how to know the issue is actually resolved
7. Document: what to capture for the post-mortem
8. Common dead-ends: what looks like the cause but isn't

Use copyable commands, link placeholders (e.g. [DASHBOARD_URL]), and avoid prose where a list works.