runbook-gen

# Runbook Generator Operation runbooks that on-call engineers can follow under pressure. Based on Google SRE practices, PagerDuty incident response, and post-mortem culture. ## Workflow Follow these steps in order when generating a runbook: 1. **Discover** — Ask the 5 Required Discovery questions (below) to scope the runbook 2. **Classify** — Map the incident to the Severity Matrix; if unclear start at Sev2 3. **Template** — Instantiate the Runbook Template with service-specific commands, time-boxes, and contacts 4. **War Room** — Configure Slack channel, Zoom bridge, shared doc, status page, and customer comms 5. **Verify** — Run through the Production Checklist before marking complete 6. **Archive** — Store the runbook in the team's on-call repo, test in a drill within the quarter When the ask is a post-mortem (not a runbook), skip steps 3-4 and use the Post-Mortem Template instead. ## 2. Required Discovery 1. **Service/System**: What is the runbook about? (API, database, cache, queue) 2. **Incident types**: What can go wrong? (down, degraded, slow, data loss) 3. **Environment**: Production, staging, or both? 4. **Team structure**: Primary, secondary, escalation contacts 5. **Existing monitoring**: Alerts, dashboards, runbooks ## 3. Severity Matrix | Severity | Definition | Response SLA | |----------|------------|--------------| | Sev1 | Service down, users impacted | Respond within 15 min | | Sev2 | Degraded performance, partial impact | Respond within 1 hour | | ...