What problem does it solve? On-call engineers woken at 3am often face runbooks that assume context they do not have, contain vague steps like "investigate the logs", or hide rollback instructions in other documents. This Skill produces runbooks written for the least-context person on the rota, so any responder can act immediately without prior knowledge. ## Core Features & Use Cases - Standardized Structure: Enforces a six-part shape covering Symptom, Verify, Impact, Fix, If-that-fails, and Afterwards. - Copy-Pasteable Commands: Requires exact commands with <angle bracket> placeholders, expected output after each step, and reversal instructions before every destructive action. - Named Escalation: Mandates naming a specific rota or person instead of escalating to an anonymous team. - Use Case: After a recurring database failover alert, generate a runbook that lets a junior engineer confirm the symptom with one command, execute numbered fix steps, and know exactly who to wake if the fix fails. ## Quick Start Write a runbook for the "disk usage above 90%" alert on our production database server, including verification, fix steps, and rollback.
