| name | eng-runbook |
| description | Engineering runbook / incident response guide with step-by-step procedures,
code snippets, and severity indicators. Use for "runbook", "incident response",
"SOP", "playbook".
|
| triggers | ["runbook","incident response","sop","playbook","procedure","troubleshooting"] |
| df | {"mode":"document","platform":"desktop","scenario":"engineering","preview":{"type":"html","entry":"index.html"},"design_system":{"requires":false}} |
Engineering Runbook Skill
Produce an engineering runbook page.
Structure
- Header: runbook title, last updated, owner, severity level badge.
- Overview: when to use this runbook, expected outcome, time estimate.
- Prerequisites: tools, permissions, access required.
- Steps: numbered list. Each step:
- Action description.
- Code block or command (copyable).
- Expected output / validation.
- Rollback command if applicable.
- Escalation: who to contact if steps fail.
- Appendix: related runbooks, logs locations, dashboards.
Rules
- Severity badges: P1=red, P2=orange, P3=yellow, P4=gray.
- Code blocks: dark background, syntax highlight via CSS classes.
- Steps are numbered, never bulleted.
data-df-id on each step.
Output
Single index.html, inline CSS.
