Operations

Deployment Runbook Prompt

Turn a deploy into a runbook anyone can execute — ordered steps, preconditions, verification at each gate, and the rollback hook, instead of tribal knowledge.

Overview

A deploy that lives in one engineer's head is a single point of failure. This prompt produces a deployment runbook: the ordered steps, the precondition checks before each, the verification that each step succeeded before moving on, and the rollback hook at every gate. The result is a document a teammate can run without you on the call.

Why This Works

Per-step verification stops a broken deploy from continuing on a bad assumption
Written preconditions catch the missing backup or approval before it bites
A runbook removes the single-person dependency from shipping

Best for

Manual or semi-automated deploys
Teams where only one person knows how to ship
Releases that need an auditable execution trail

Not for

Designing rollback triggers specifically — use the Rollback Plan Prompt
Fully automated CI/CD where the pipeline is the runbook

Use cases

Documenting a deploy so anyone on the team can run it
Turning a manual deploy into a repeatable checklist
Onboarding a new engineer onto the release process

Customize This Resource

Opens this resource in the related tool with the fields pre-filled. Customize role, tone, and behavior rules — then generate your prompt.

Prompt Template

ROLE
You are a release engineer writing a deployment runbook a teammate could execute without you present.

INPUT
What's being deployed and how:
[Describe the change, environments, and deploy mechanism]

PRODUCE A RUNBOOK
For the whole deploy and for each step:
- PRECONDITIONS: what must be true before this step runs (checks, approvals, backups).
- ACTION: the exact action to take, unambiguously.
- VERIFICATION: how to confirm this step succeeded before continuing.
- ON FAILURE: what to do if verification fails (retry, rollback hook, stop-and-escalate).

Structure: Pre-deploy checks → Deploy steps (ordered) → Post-deploy verification → Sign-off.

RULES
- No step may assume context the executor doesn't have written down.
- Every step that changes production must have a verification and a failure path.

OUTPUT
A runbook with numbered steps, each carrying its preconditions, verification, and on-failure action.

Related Resources

Explore more resources that work well with this one.

Related Tools

Markdown Output Builder

Tip: Save time by exploring related resources and tools that integrate with this workflow.

Explore all resources