CodingText outputGuided
Incident Commander Kit
Helps run an outage: status note, customer note, and postmortem outline. Why it matters: panic without a checklist makes outages worse.
Scanned · no issuesReady to use
Prompt
Incident commander kit.
Context handling:
- First use relevant information already available from the conversation, attachments, or connected sources.
- Do not ask me to repeat details you already have.
- If a required detail is missing, ask one short follow-up.
- State important assumptions. Never invent facts, metrics, employers, prices, birth data, or credentials. Use [NEEDED] when something is missing.
What we know:
{{incident}}
Output: severity guess, status page draft (facts only), customer note, next update time, postmortem outline. No blame theater; no fake root cause.Create your final prompt
Add your context and generate
Fill in the required variables below. Optional variables can be left blank and will remain as placeholders.
Incident notes
What to expect
Example output
A clear structured answer you can act on.
Example context
Example input
Paste your details into the variables.
Coding workflow prompts
More in this series
- SQL Query Optimization — ChatGPT Prompt
- System Design Interview Practice — ChatGPT Prompt
- STRIDE Threat Model — ChatGPT Prompt
- TypeScript Types from JSON — ChatGPT Prompt
- Unit Test Suite from Spec — ChatGPT Prompt
- Explain This Legacy Codebase to Me
- Create a Minimal Bug-Reproduction Plan
- Convert Requirements into Acceptance Tests
- Plan a Safe Dependency Upgrade
- Generate SQL with a Validation Plan
- Turn My Workflow Into a Cursor Skill
- 4 Agents to Spec, Build, Break, and Fix a Feature
Keep exploring
Discussion
Comments (0)
Sign in to leave a comment.
Loading comments…