Runbook Generator

alirezarezvani/claude-skills/engineering/skills/runbook-generator

by alirezarezvani19392f7a0826No license27K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 5 weeks ago

Generate operational runbooks from a service name — deployment, incident response, maintenance, and rollback workflows. Templated structure customizable per environment. Use when documenting on-call procedures for a new service, standardizing incident response across teams, or producing runbooks before launching to production.

Includes scriptsDevOps & Cloud
AI-generated overview

Generates operational runbook skeletons for a service, covering deployment, incident response, maintenance and rollback.

What it does
This skill produces operational runbook documents from a service name using a command-line script. It emits a templated skeleton with standard sections for start, stop, health checks and rollback, plus placeholders for escalation and incident handling. Output can be printed to stdout or written to a file, and reference templates for deployment and incident playbooks are included.
When to use it
Use it when a service lacks a runbook and needs a baseline, when runbooks are inconsistent across teams, when onboarding on-call staff requires standardized operations documentation, or when scaffolding runbooks before a production launch.
Requirements
Requires Python 3 to run the bundled script scripts/runbook_generator.py. No credentials or network access are described; the skill ships an executable script and a reference template file.

Runbook Generator

Tier: POWERFUL
Category: Engineering
Domain: DevOps / Site Reliability Engineering


Overview

Generate operational runbooks quickly from a service name, then customize for deployment, incident response, maintenance, and rollback workflows.

Core Capabilities

  • Runbook skeleton generation from a CLI
  • Standard sections for start/stop/health/rollback
  • Structured escalation and incident handling placeholders
  • Reference templates for deployment and incident playbooks

When to Use

  • A service has no runbook and needs a baseline immediately
  • Existing runbooks are inconsistent across teams
  • On-call onboarding requires standardized operations docs
  • You need repeatable runbook scaffolding for new services

Quick Start

bash
# Print runbook to stdoutpython3 scripts/runbook_generator.py payments-api
# Write runbook filepython3 scripts/runbook_generator.py payments-api --owner platform --output docs/runbooks/payments-api.md

Recommended Workflow

  1. Generate the initial skeleton with scripts/runbook_generator.py.
  2. Fill in service-specific commands and URLs.
  3. Add verification checks and rollback triggers.
  4. Dry-run in staging.
  5. Store runbook in version control near service code.

Reference Docs

  • references/runbook-templates.md

Common Pitfalls

  • Missing rollback triggers or rollback commands
  • Steps without expected output checks
  • Stale ownership/escalation contacts
  • Runbooks never tested outside of incidents

Best Practices

  1. Keep every command copy-pasteable.
  2. Include health checks after every critical step.
  3. Validate runbooks on a fixed review cadence.
  4. Update runbook content after incidents and postmortems.

Source and attribution

Source:alirezarezvani/claude-skillsinengineering/skills/runbook-generatorat commit19392f7

License: No license

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

Report or request removal