Incident Runbook to Automation Conversion Prompt
Analyze an existing manual incident runbook and produce a phased plan to convert its steps into automation, separating what is safe to automate now from what should stay human-driven.
- Target user
- SRE and incident-management teams reducing manual response toil
- Difficulty
- Intermediate
- Tools
- Claude, ChatGPT
The prompt
You are a senior SRE who converts manual incident runbooks into safe, staged automation. I will provide: - The full text of an existing runbook (diagnosis + remediation steps) - The tools available to automate (orchestrator, scripts, ChatOps, ticketing) - The frequency and typical severity of the incident - Any steps that have historically gone wrong Your job: 1. **Decompose** — break the runbook into atomic steps and label each as diagnostic (read-only) or mutating. 2. **Automation candidacy** — score each step on safety, frequency, and determinism; recommend automate-now, automate-with-approval, or keep-manual. 3. **Sequence the rollout** — start with read-only diagnostics and notifications, then add gated remediation; never automate the riskiest step first. 4. **Implementation sketch** — for each automated step, outline the trigger, the action, and the verification check. 5. **Human-in-the-loop** — define where approvals, confirmations, and escalation handoffs sit. 6. **Rollback** — specify how each automated remediation is reversed if it fails. 7. **Metrics** — define how to measure toil reduction and automation accuracy over time. Output as: (a) the annotated step table, (b) the phased rollout plan, (c) the human-approval map, (d) success metrics. Recommend automating diagnostics and notifications first; require explicit human approval and a tested rollback for every mutating remediation step.
Run this prompt with AI
Test it, get an AI-improved version, or compare models — live in the Prompt Workspace. No copy-paste.
Related prompts
-
Incident Timeline to Runbook Generation Prompt
Turn the messy timeline of a just-resolved incident — chat logs, commands run, graphs, and decisions — into a clean, reusable runbook with detection signals, decision points, exact verified steps, and a clear marking of which steps are safe to later automate.
-
Runbook to Approval-Gated Workflow Design Prompt
Convert a manual, free-text operational runbook into an automated workflow that keeps humans in the loop by inserting approval gates, dry-run previews, and read-only checks at exactly the steps where judgment or blast radius demands sign-off.
-
Intelligent Runbook Selection Engine Prompt
Design an AI-assisted layer that maps an incoming alert or incident to the right runbook (or flags that none exists), ranks candidates by signal match, and hands the on-call a confidence-scored shortlist instead of a wiki search.
-
Toil Task Automation with Rollback Plan Prompt
Safely automate a repetitive toil task by first proving the manual steps, then wrapping them in an automation that has a dry-run, an explicit undo path, verification after each change, and a kill switch — so saving time never trades away the ability to reverse a mistake.
More Automation prompts & error guides
Browse every Automation prompt and troubleshooting guide in one place.
Reading prompts? Get all 500 in one free PDF
500 battle-tested, copy-paste AI prompts engineered by a senior systems engineer — every one with fill-in placeholders and safety/back-out notes. Drop your email and it's yours.
- 500 prompts: Linux · Kubernetes · Terraform · OpenStack · GitLab · Docker · Monitoring · Incident Response
- Instant PDF download — yours free, forever
- Plus one practical AI-workflow email a week (no spam)
Single opt-in · unsubscribe anytime · no spam.