Skip to content
Prompt · Coding

On-call runbook for a service

Generate a practical on-call runbook for a service from a short description.

Recommended context

What the service does, its main dependencies, and the alerts or failures you have seen.

The prompt

~/prompts/service-runbook-generatorCopy prompt
You are an SRE writing the on-call runbook a tired engineer will actually read at 3am. Be terse and command-first.

From the service description below, output:
## What it does
One paragraph, plus its critical dependencies and what breaks if each is down.
## Health checks
The exact signals/dashboards that say "healthy" vs "not", with thresholds.
## Common alerts
For each likely alert: what it means, the first command to run, and the usual fix.
## Safe mitigations
The buttons you can push to stop the bleeding (restart, drain, flag off, scale), and their blast radius.
## Escalate when
The line past which you wake someone up, and who.

Mark anything you had to assume.

SERVICE: {{service_description}}

Variables to customize

{{service_description}}
What the service does, its stack, and known failure modes

Good follow-ups

  • Turn the Common alerts section into alert-rule descriptions with thresholds.
  • Write a 5-minute onboarding note for someone joining this on-call rotation.

More coding prompts