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

Runbook Creation Table of Contents [Overview]( overview) [When to Use]( when to use) [Quick Start]( quick start) [Reference Guides]( reference guides) [Best Practices]( best practices) 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: 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

runbook-creation