Skip to main content

Your buyers are asking AI. Are you the answer?

Find out with OptimizeCamp →

Incident Response Runbook

Create step-by-step incident response runbooks for common failure modes with escalation paths

SREDevOpsOperations

About the Incident Response Runbook Prompt Template

This technical template assigns the AI the role of a site reliability engineer who writes clear, actionable incident runbooks that anyone on-call can follow under pressure, so the prompt it builds is framed by genuine subject-matter expertise rather than a generic request.

What it does: Create an incident response runbook for your incident in your system with your severity severity handling.

You fill in 6 fields (3 required, 3 optional), and SurePrompts assembles a complete, structured prompt you can paste straight into ChatGPT, Claude, or Gemini.

Create technical documentation, code explanations, and developer-focused content with AI.

How to Use This Template

  1. 1

    Fill in Incident Type

    e.g., Database connection pool exhaustion, API latency spike > 5s, Payment processing failures

  2. 2

    Fill in System / Service

    e.g., Production API cluster, Payment service, User authentication system

  3. 3

    Fill in Severity Levels to Cover

    Enter the severity levels to cover for your prompt.

  4. 4

    Fill in Tech Stack

    e.g., AWS, Kubernetes, PostgreSQL, Redis, Datadog

  5. 5

    Fill in On-Call Team

    e.g., Platform team, Backend engineers, SRE team

  6. 6

    Fill in Monitoring / Alerting Tools

    e.g., Datadog, PagerDuty, Grafana, CloudWatch, Sentry

  7. 7

    Copy your prompt

    Click the copy button to copy your generated prompt, then paste it into your preferred AI tool.

Template Fields

Every field below maps to a part of the finished Incident Response Runbook prompt. Required fields shape the core request; optional fields add detail and control.

Incident TypetextRequired

A required input that takes a short line of text.

Example: e.g., Database connection pool exhaustion, API latency spike > 5s, Payment processing failures

System / ServicetextRequired

A required input that takes a short line of text.

Example: e.g., Production API cluster, Payment service, User authentication system

Severity Levels to CoverselectRequired

A required input that takes one option from a list. Choose from 3 preset choices.

Available choices:

All levels (P1-P4)Critical only (P1-P2)Standard (P2-P3)
Tech Stacktext

An optional input that takes a short line of text.

Example: e.g., AWS, Kubernetes, PostgreSQL, Redis, Datadog

On-Call Teamtext

An optional input that takes a short line of text.

Example: e.g., Platform team, Backend engineers, SRE team

Monitoring / Alerting Toolstext

An optional input that takes a short line of text.

Example: e.g., Datadog, PagerDuty, Grafana, CloudWatch, Sentry

Use This Template

Related Resources

Blog Post

16 AI Prompts for Manufacturing Operations: Quality, Downtime, and SOPs

Use these AI prompts to structure manufacturing shift handoffs, quality investigations, maintenance planning, work instructions, and continuous improvement.

Blog Post

AI SOP Writing Prompts (2026): Standard Operating Procedures That Work

Prompt patterns for SOPs — process decomposition, step ordering, exception handling, and ownership. Structure the prompt and the SOP is usable.

Blog Post

5 Prompt Patterns for API Documentation and Integration

Copy-paste prompt templates for writing API docs, generating integration guides, troubleshooting endpoints, and creating SDK examples.

Blog Post

5 Prompt Patterns for AI-Assisted Code Review

Five prompt patterns for thorough AI code reviews. Covers security audits, performance checks, readability, bug detection, and architecture review.

Related Templates

Bug Report

Write a clear, actionable bug report that developers can act on immediately

README Generator

Create a professional README.md for any project or repository

API Endpoint Documentation

Document an API endpoint with request/response examples

Git Commit Message

Write clear, conventional commit messages with proper scope and description