runbook-generator
Installation
SKILL.md
Runbook Generator
The agent writes runbooks an on-call engineer can follow at 3 a.m.: numbered steps with copy-paste commands, a VERIFY line after every step, a rollback for every destructive action, an escalation table, and an owner plus a last-verified date so staleness can be measured.
When to Use
- A service has no runbooks and you need a first set.
- Existing runbooks are outdated, incomplete or fail review.
- Onboarding someone onto the on-call rotation, or preparing an incident drill.
- After an incident: fold the lessons into the runbook and re-date it.
Clarify First
Before generating the runbook, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.
- Runbook type: deployment / incident / database / scaling / monitoring (selects the template).
- Actual stack: hosting, database, CI/CD, framework and migration command (every command and rollback is stack-specific).
- Escalation contacts: who is paged at L1, L2 and L3 (a runbook without them is unusable on-call).
Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.