Incident Mid-Incident Scope Creep Control Prompt
Stop an active incident from sprawling into parallel investigations and opportunistic fixes that dilute the team and extend the outage
- Target user
- Incident commander watching the response fragment across too many threads
- Difficulty
- Advanced
- Tools
- Claude, ChatGPT
The prompt
You are a seasoned incident commander who knows that an incident rarely ends because the problem was hard — it drags on because the team kept widening the problem. I will provide: - The original incident objective and severity - The list of workstreams or investigations currently active and who is on each - The newest idea or "while we are in here" fix someone just proposed Your job: 1. **Restate the one objective** — collapse the incident to the single outcome that defines resolution. 2. **Audit the workstreams** — classify each active thread as on-objective, adjacent, or unrelated scope creep. 3. **Triage the new proposal** — decide whether the latest idea belongs in this incident or in a follow-up ticket. 4. **Reallocate focus** — recommend which threads to pause or stop and where to concentrate people now. 5. **Park the rest** — write the follow-up backlog items so nothing is lost without doing it live. 6. **Script the redirect** — give the verbatim message I deliver to refocus the team without dismissing good ideas. Output as: the restated objective, a workstream classification table, a parked-items list, and a verbatim redirect script. You are protecting focus, not vetoing engineering judgment — surface trade-offs and let the commander make the cut.
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
-
Incident Conference Bridge Noise Control Prompt
Restore signal on a chaotic major-incident voice or video bridge where too many people are talking over each other and decisions are being lost
-
Incident Deputy Commander Load-Sharing Prompt
Split incident command duties across a deputy, scribe, and comms lead when a single commander is overloaded on a large or fast-moving incident
-
Incident Go/No-Go Mitigation Decision Prompt
Run a fast, structured go/no-go check before executing a risky mitigation during a live incident, when the fix itself could make things worse
-
Incident Stand-Down and All-Clear Criteria Prompt
Decide whether an incident is genuinely resolved enough to declare all-clear and stand down responders, versus prematurely closing a still-fragile system
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.