RW
Runbook Writer
🟢 Production-Ready🕐 updated 2026-07-14
🔷 SkillSpec L3
pm-engineering
Write an operational runbook for a service, incident type, or deployment procedure. Use when asked to write a runbook, create an ops guide, document an operational procedure, or prepare an incident response playbook. Produces a runbook with overview, prerequisites, step-by-step procedures, rollback steps, troubleshooting table, and escalation paths.
What to give it
▸What the runbook is for — e.g. deploying the payment service, responding to a database failover, rotating API keys
▸Runbook type — Deployment / Incident Response / Maintenance / Disaster Recovery
▸System / service name and what it does — brief description
▸Audience — new on-call engineers / experienced SREs / DevOps team
▸Tech stack — where relevant — e.g. Kubernetes, AWS RDS, Node.js
▸Monitoring tools — e.g. Grafana, Datadog, CloudWatch, Splunk — used to name specific dashboards and alert links in the steps
▸Key environment details — e.g. Kubernetes cluster name, AWS account/region, relevant namespaces or resource names — paste what's relevant for exact commands
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓Every step has an exact command (no "run the deploy script")
✓Expected output is specified for each step so engineer knows if it worked
✓Failure path is explicit for each step (not "if it fails, investigate")
✓Rollback procedure is complete and independently testable
✓Escalation table has no cells containing only "[Team name]" — every row must either have a real contact or be explicitly flagged as [FILL IN: on-call rotation link]
✓Rollback section contains at least one concrete command (not left as "[rollback command]" placeholder)
✓Runbook can be followed by someone who has never touched this system
⚠️ What it refuses to do
Do not write steps as vague actions like "run the deploy script" — every step must include the exact command
Do not leave the rollback section as a placeholder — a runbook without a tested rollback procedure is incomplete and dangerous
Do not omit expected output for each step — without it, the on-call engineer cannot tell if the step succeeded
Do not write escalation contacts as "[Team name]" — every escalation row must have a real contact or an explicit flag to fill in
Do not assume the reader knows the system — write for someone who has never touched it before
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcpStart with
Related skills
🔌 Embed this skill
Drop this on your blog, docs, or site — it renders a "Run this skill" card:
<div data-pm-skill="runbook-writer"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>💬 Discussion
Runbook Writer is one of 1078 open-source professional AI agent skills — all SkillSpec L3.
Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog