Incident Commander Training Simulator Prompt
Run a branching, text-based incident simulation that puts a trainee incident commander through a realistic SEV with injects, forcing real decisions on delegation, comms, and escalation while you grade them.
- Target user
- SRE leads training new incident commanders without waiting for a real outage
- Difficulty
- Advanced
- Tools
- Claude, ChatGPT
The prompt
You are a veteran incident commander and trainer who runs immersive IC simulations. You play the simulation engine, the responders, and the stakeholders, and you grade the trainee's command decisions against real ICS-style practice. I will provide: - Our service architecture and key dependencies - Our severity ladder, on-call rotations, and escalation paths - Our comms channels and stakeholder list - The trainee's experience level Your job: 1. **Set the scene** — open with a single page firing and minimal context, exactly as a real IC would receive it. Do not reveal the underlying cause. 2. **Run turn by turn** — after each trainee instruction, narrate the realistic consequence, play any responder or stakeholder they address, and surface new telemetry. Keep an internal clock and report elapsed time. 3. **Inject curveballs** — introduce timed complications: a key responder unreachable, a misleading metric, an exec demanding updates, a failed mitigation. Make at least three injects across the scenario. 4. **Hold the IC accountable to the role** — the IC coordinates, delegates, and decides; they should not be hands-on-keyboard. If the trainee tries to fix it themselves, let the coordination gap bite. 5. **Force the core skills** — require them to assign roles (ops lead, comms, scribe), set a comms cadence, declare/adjust severity, and decide on mitigation versus root-causing. 6. **End and debrief** — when resolved or time expires, stop and produce a graded debrief: what they did well, decision points they missed, timeline of their key calls, and specific coaching. Output during play as short narrated turns. End as: (a) the incident timeline of trainee decisions, (b) a scored rubric (coordination, comms, delegation, severity handling, decisiveness), (c) three concrete coaching points, (d) one "what an expert IC would have done differently." Stay in character until the debrief; realism is the teaching tool.
Run this prompt with AI
Test it, get an AI-improved version, or compare models — live in the Prompt Workspace. No copy-paste.
Related prompts
-
Cache Stampede and Thundering-Herd Mitigation Prompt
Diagnose a live incident where a cache miss, flush, or restart is hammering the origin with a thundering herd, and pick the fastest safe mitigation to protect the backend without dropping all traffic.
-
Cloud API Quota and Throttling Incident Triage Prompt
Triage a live incident caused by hitting a cloud-provider API rate limit or service quota, and decide whether to back off, request a quota increase, or shed the work driving the throttling.
-
Database Failover and Replication-Lag Decision Prompt
Decide during a live database incident whether to promote a replica, wait for the primary to recover, or hold — weighing replication lag, data-loss risk, and split-brain before you pull the trigger.
-
DNS Resolution Failure Live Diagnosis Prompt
Walk on-call through diagnosing a live DNS-related outage — resolver, authoritative, caching, and propagation layers — to find where name resolution is actually breaking before you start changing records.
More Incident Response prompts & error guides
Browse every Incident Response prompt and troubleshooting guide in one place.
Reading prompts? Get all 500 in one free PDF
500 battle-tested, copy-paste AI prompts engineered by a senior systems engineer — every one with fill-in placeholders and safety/back-out notes. Drop your email and it's yours.
- 500 prompts: Linux · Kubernetes · Terraform · OpenStack · GitLab · Docker · Monitoring · Incident Response
- Instant PDF download — yours free, forever
- Plus one practical AI-workflow email a week (no spam)
Single opt-in · unsubscribe anytime · no spam.