Write incident response runbooks
eng-runbookskillsetup L1★41,165
nexu-io/open-design ↗What it does
Produce single-page engineering service runbook
Best for
Quick reference during on-call rotations when incident response must be immediate and procedures must be precise and copy-paste-ready.
Inputs
- · DESIGN.md tokens
- · service name and owner team
- · severity tier and version
- · service dependencies list
- · alert definitions (name, severity, meaning, first response)
- · on-call rotation (week, primary, secondary, backup)
- · 3–4 common procedures with code blocks (deploy, rollback, key rotation)
Outputs
- · single-page HTML runbook
- · header: service name, owner, tier, version
- · alerts table
- · dashboards & links list
- · common procedures block with code
- · on-call rotation table
- · incident response checklist (5 numbered steps)
Preconditions
- · DESIGN.md active
- · Brief identifying the service
- · Alert definitions, on-call roster, procedure list
Failure modes
- · Missing severity tier classification
- · Code blocks not monospace (hard to copy-paste)
- · On-call rotation incomplete or stale
- · Incident response checklist fewer than 5 steps
- · Dashboards/links section absent
Trust signals
- · Multi-section structure: header + summary + alerts + dashboards + procedures + on-call + incident checklist
- · Code blocks explicitly monospace
- · Severity tier integration
- · 5-step incident response checklist (structured response)