AI Ops Incident Response Commander

Coordinate technical incidents with structured triage, mitigation planning, stakeholder updates, and post-incident follow-up.

The Prompt

You are an incident commander supporting a live technical incident. Help the team organize the response, reduce confusion, and keep communication disciplined.

## 1. Incident Snapshot
Summarize:
- What appears to be broken
- Earliest known detection time
- Affected systems or users
- Current severity assumption
- Known unknowns

## 2. Triage Framework
List:
- Most likely root-cause hypotheses
- Fastest validation checks
- Immediate mitigation options
- Risk of each mitigation step
- Whether rollback, failover, or containment should be considered

## 3. Coordination Plan
Create:
- Roles needed right now
- Owner for each workstream
- 15-minute action plan
- Next decision checkpoint
- Evidence to collect for later postmortem

## 4. Communication Outputs
Draft:
- Internal incident update
- Executive summary
- Customer-facing status update if appropriate

## 5. Recovery and Follow-Up
Provide:
- Exit criteria for resolving the incident
- Follow-up monitoring checklist
- Post-incident review agenda
- Preventive actions to evaluate after stabilization

## 6. Output Format
Return:
1. Incident snapshot
2. Hypothesis table
3. Immediate action plan
4. Communications drafts
5. Resolution criteria
6. Postmortem notes starter

Incident details:
[PASTE ALERTS, LOGS, SYMPTOMS, TEAM NOTES]

Optional context:
- Service type: [API / SAAS / INTERNAL TOOL / DATA PIPELINE]
- Customer impact: [DESCRIBE]
- Known constraints: [NO ROLLBACK / COMPLIANCE / DATA RISK / ETC]

How to Use This Prompt

1. Paste raw symptoms first, even if they are incomplete.
2. Keep the first pass focused on triage and mitigation, not perfect root cause.
3. Ask for separate drafts for internal and external communication.
4. Use the evidence checklist to support a better postmortem later.
5. Re-run the prompt when the incident state changes materially.

Example Input

Service type: SaaS API
Customer impact: Elevated 500 errors on write endpoints for EU customers
Known constraints: Rollback possible but may affect recent schema changes
Incident details: [alerts, logs, deploy notes]

Example Output

1. Incident Snapshot

Likely write-path regression tied to a recent schema or deployment change, currently concentrated in EU traffic.

2. Immediate Action Plan

• Validate whether the error rate correlates with the latest deployment
• Check whether the issue is region-specific or data-shape-specific
• Prepare rollback while a second engineer validates blast radius

3. Communication Draft

We are investigating elevated API error rates affecting some write operations. Mitigation is in progress and the next update will be provided in 15 minutes.

When This Prompt Is Most Useful

Use this prompt when you need help with ai ops incident response commander but do not want a generic answer. It works best for operators, founders, automation builders, and teams turning repeated work into a reliable AI-assisted process who already have some context and want the AI to organize it into a workflow map, SOP, automation checklist, prompt chain, or human review plan. The prompt is intentionally written to slow the model down: it asks for the goal, missing information, assumptions, reasoning, and a review checklist instead of jumping straight to a polished answer.

This is especially useful when the task has tradeoffs. A simple prompt may produce a confident answer that sounds good but misses constraints. This version makes the model surface those constraints before it gives recommendations, which makes the output easier to edit, verify, and reuse.

Inputs to Prepare

Before running the prompt, gather:

• The real goal or decision you are trying to support
• The audience, customer, learner, stakeholder, or user involved
• Any source material the AI should use instead of guessing
• Constraints such as deadline, format, budget, word count, platform, or policy
• Examples of good and bad outputs if you have them
• The exact tone you want the final answer to use

For this page, the most important context is: trigger, inputs, systems involved, decision points, review owner, failure cases, and what should happen after output is generated. If you leave that out, the model may still respond, but the result will usually be generic.

Example Input

Workflow: turn support tickets into weekly product insights. Inputs: tags, plan, ticket text. Output: themes, quotes, and follow-up tasks.

How to Review the Output

Do not use the first answer blindly. Check whether it:

• makes handoffs and ownership explicit
• defines what the AI should not decide
• includes monitoring or review checkpoints
• makes assumptions visible instead of hiding them in confident language
• gives you something you can act on, test, or revise within the same work session

If the answer feels generic, reply with: “Make this more specific to my context. Remove generic advice, name the tradeoffs, and show the exact changes you would make.” If the answer is too long, ask for a shorter version that keeps the checklist and decision points.

Common Failure Modes

• Too little context: the AI fills gaps with generic advice.
• No review criteria: the output sounds polished but is hard to judge.
• Unclear audience: the answer may optimize for the wrong reader or use the wrong tone.
• Overclaiming: the model may invent certainty when the source material is weak.

The fix is to add concrete inputs and ask for assumptions, alternatives, and review criteria before you use the final output.

Practical Variations for AI Ops Incident Response Commander

• SOP mode: Ask for trigger, input, output, owner, and acceptance criteria for each step.
• Automation mode: List systems involved and ask where AI should draft, classify, summarize, or route work.
• Monitoring mode: Ask for quality checks, failure signals, and human review points.

Follow-Up Prompts

Use these after the first answer:

• “Rewrite this using only the context I provided. Label assumptions instead of hiding them.”
• “Give me a conservative version, a direct version, and a version optimized for speed.”
• “Create a final review checklist I can use before I publish, send, ship, or present this.”

What Makes This Page Different

This page is useful when you are working on ai ops incident response commander and need more than a blank chat box. It gives you a starting prompt, context checklist, review criteria, and practical variations so the answer can be tested instead of merely accepted. If your task is broader, start with a workflow guide first, then come back to this prompt once the input, audience, and success criteria are clear.