Runbook Creation

aj-geddes/useful-ai-prompts/skills/runbook-creation

by aj-geddes3f5182cfd739No license355 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 7 months ago

Create operational runbooks, playbooks, standard operating procedures (SOPs), and incident response guides. Use when documenting operational procedures, on-call guides, or incident response processes.

Includes scriptsDevOps & Cloud Documents & Office

AI-generated overview

Creates operational runbooks, SOPs, and incident response guides with step-by-step procedures.

What it does: Produces structured operational runbooks covering incident response, standard operating procedures, on-call playbooks, maintenance, disaster recovery, and escalation. It supplies reference guides for symptoms, investigation, resolution, verification, communication, and post-incident review, plus a validation script and an API scaffold template. Output is a written runbook document with severity levels, response times, exact commands, and verification steps.
When to use it: Use when documenting operational procedures, on-call guides, or incident response processes. It fits teams that need consistent escalation paths, severity definitions, and communication templates for outages or maintenance.
Requirements: No special runtime or credentials are stated. The skill ships an executable validation script (scripts/validate-api.sh) and a YAML scaffold template, so a shell environment is needed to run the script.

Overview

Create comprehensive operational runbooks that provide step-by-step procedures for common operational tasks, incident response, and system maintenance.

When to Use

Incident response procedures
Standard operating procedures (SOPs)
On-call playbooks
System maintenance guides
Disaster recovery procedures
Deployment runbooks
Escalation procedures
Service restoration guides

Quick Start

Minimal working example:

markdown

# Incident Response Runbook
## Quick Reference
**Severity Levels:**
- P0 (Critical): Complete outage, data loss, security breach- P1 (High): Major feature down, significant user impact- P2 (Medium): Minor feature degradation, limited user impact- P3 (Low): Cosmetic issues, minimal user impact
**Response Times:**
- P0: Immediate (24/7)- P1: 15 minutes (business hours), 1 hour (after hours)- P2: 4 hours (business hours)- P3: Next business day
**Escalation Contacts:**
- On-call Engineer: PagerDuty rotation- Engineering Manager: +1-555-0100- VP Engineering: +1-555-0101- CTO: +1-555-0102
// ... (see reference guides for full implementation)```
## Reference Guides
Detailed implementations in the `references/` directory:
| Guide | Contents ||---|---|| [Symptoms](references/symptoms.md) | Symptoms, Severity: P0 (Critical), Initial Response (5 minutes) || [Investigation Steps](references/investigation-steps.md) | Investigation Steps || [Resolution Steps](references/resolution-steps.md) | Resolution Steps || [Verification](references/verification.md) | Verification || [Communication](references/communication.md) | Communication || [Post-Incident](references/post-incident.md) | Post-Incident |
## Best Practices
### ✅ DO
- Include quick reference section at top- Provide exact commands to run- Document expected outputs- Include verification steps- Add communication templates- Define severity levels clearly- Document escalation paths- Include useful links and contacts- Keep runbooks up-to-date- Test runbooks regularly- Include screenshots/diagrams- Document common gotchas
### ❌ DON'T
- Use vague instructions- Skip verification steps- Forget to document prerequisites- Assume knowledge of tools- Skip communication guidelines- Forget to update after incidents

# Incident Response Runbook
## Quick Reference
**Severity Levels:**
- P0 (Critical): Complete outage, data loss, security breach- P1 (High): Major feature down, significant user impact- P2 (Medium): Minor feature degradation, limited user impact- P3 (Low): Cosmetic issues, minimal user impact
**Response Times:**
- P0: Immediate (24/7)- P1: 15 minutes (business hours), 1 hour (after hours)- P2: 4 hours (business hours)- P3: Next business day
**Escalation Contacts:**
- On-call Engineer: PagerDuty rotation- Engineering Manager: +1-555-0100- VP Engineering: +1-555-0101- CTO: +1-555-0102
// ... (see reference guides for full implementation)```
## Reference Guides
Detailed implementations in the `references/` directory:
| Guide | Contents ||---|---|| [Symptoms](references/symptoms.md) | Symptoms, Severity: P0 (Critical), Initial Response (5 minutes) || [Investigation Steps](references/investigation-steps.md) | Investigation Steps || [Resolution Steps](references/resolution-steps.md) | Resolution Steps || [Verification](references/verification.md) | Verification || [Communication](references/communication.md) | Communication || [Post-Incident](references/post-incident.md) | Post-Incident |
## Best Practices
### ✅ DO
- Include quick reference section at top- Provide exact commands to run- Document expected outputs- Include verification steps- Add communication templates- Define severity levels clearly- Document escalation paths- Include useful links and contacts- Keep runbooks up-to-date- Test runbooks regularly- Include screenshots/diagrams- Document common gotchas
### ❌ DON'T
- Use vague instructions- Skip verification steps- Forget to document prerequisites- Assume knowledge of tools- Skip communication guidelines- Forget to update after incidents

Source and attribution

Source:aj-geddes/useful-ai-promptsinskills/runbook-creationat commit3f5182c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Runbook Creation

Runbook Creation

Table of Contents

Overview

When to Use

Quick Start

Source and attribution

More from aj-geddes/useful-ai-prompts

Xss Prevention

Wireframe Prototyping

Web Performance Optimization

Vue Application Structure

Visual Regression Testing

User Persona Creation

More in DevOps & Cloud

Playwright Devops

M5 Onboard

Yeet

Runbook

Incident Response

Deploy Checklist