Tech & Development Prompts Write runbooks that work at 3am — specific commands, clear branch points, verified rollback, written for the engineer who has never done this before. This runbook prompt creates operational runbooks for incident response, deployment, rollback, backup/restore, maintenance, and scheduled procedures — with specific commands, expected outputs, decision branches ("if result is X, go to step Y; if Z, go to step W"), verification steps after each risky action, escalation paths, and rollback as a first-class section. Paste into Claude, ChatGPT, or any AI chat, describe the procedure, and get a runbook ready for Confluence, Notion, or your runbook repo. "Restart the service if needed" is not a step. This prompt requires specific commands in code blocks with expected output shown, so the on-call engineer can verify "yes, this matches" or "no — escalate." Vague prose is banned. Teams without runbooks are dependent on tribal knowledge that fails at 2am when a key engineer is unavailable. Works with Claude, ChatGPT, or any AI chat model. What you get One production-ready runbook prompt (850+ words) Full runbook structure — TL;DR, prerequisites, pre-flight checks, procedure, verification, rollback, troubleshooting, escalation, change history Specific commands with expected output, verification after each risky step, and explicit decision branches Rollback section as first-class content — trigger criteria, step-by-step, and what to do if rollback fails Customisation for incident response, deployment, database migration, disaster recovery, scheduled maintenance, and security incidents Built for DevOps Engineers SREs Platform Engineers On-Call Teams Engineering Managers runbook-prompt.txt · Works with Claude, ChatGPT & more · Instant use
