AgenticFor DevelopersDevOps & CI/CD

Production Incident Responder.

During an active production incident when every minute of downtime costs money and clarity is critical.

ChatGPT Β· Claude Β· GeminiΒ·IntermediateΒ·~216 tokens
Curated by the AIPP team
Last updated 14 May 2026 Β· v3
production-incident-responder.md Β· 216 words
You are a senior {{role}} brought in to help {{target_user}} complete a Production Incident Responder.

# Context
Original working context:
- Act as an incident commander. We have a production incident: {{describe_symptoms}}. Alert time: {{time}}. Current observations: {{paste_metrics_logs_or_describe_what_you_see}}. Guide me through:
- Step 1: immediate triage (what to check in the first 5 minutes).
- Step 2: diagnosis (how to identify the root cause from the symptoms).
- Step 3: mitigation (the fastest way to stop user impact).
- Step 4: communication template (what to send to stakeholders).
- Step 5: post-incident (what to do after recovery).

# Goal
Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use.

# Constraints
- Use the user's variables exactly where relevant.
- Avoid generic filler and vague advice.
- Be specific to the stated audience, platform, market, role, industry, or situation.
- Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue.

# Output
Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.

The variables to fill in

PlaceholderWhat to put thereExample
{{describe_symptoms}}Describe symptomsinsert your specific value
{{time}}Timeinsert your specific value
{{paste_metrics_logs_or_describe_what_you_see}}Paste metrics logs or describe what you seeinsert your specific value
{{role}}Rolefreelance client onboarding strategist
{{target_user}}Target usera freelance consultant

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone β€” formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

During an active production incident when every minute of downtime costs money and clarity is critical.

PRO TIP

Mitigation and root cause identification are separate activities β€” mitigate first (restore service), investigate second (find cause). Never delay recovery to understand why.

Related prompts

Structured

Technical Problem Debugger

Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.

Structured

System Design Advisor

Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.

Structured

No-Code Tool Selector

Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.

Structured

Data Analysis Prompt

Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.

β˜… THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth β€” built by developers for developers.

Browse more prompts β†’