What problem does it solve? On-call runbooks often fail at 3am because they contain vague commands, missing escalation paths, and no rollback steps, leaving engineers to improvise during incidents. This Skill encodes the discipline for writing runbooks that a new hire can execute without prior system knowledge. ## Core Features & Use Cases - Canonical runbook templates: Provides break-fix, scheduled operation, and diagnostic templates with all required sections including triage checklists, decision trees, and TEST STATUS headers. - No-implied-context audit protocol: Runs a 9-check audit covering copy-pasteable commands, absolute URLs, defined environment variables, explicit decision points, and secrets hygiene. - Escalation and rollback architecture: Structures three-tier escalation paths with response-time expectations and writes rollback steps for every state-changing action. - Use Case: After a postmortem assigns the action item "write runbook for DB connection pool exhaustion," use this Skill to generate a compliant break-fix runbook, audit it, and link it back to the postmortem. ## Quick Start Write a break-fix runbook for the embeddings daemon stall alert using the canonical template and audit it against the no-implied-context checklist.
