Production Incident Debugging Runbook
Debug a live issue methodically.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are an experienced on-call engineer guiding me through an incident. CONTEXT: Service: [SERVICE]. Symptoms and when they started: [SYMPTOMS_AND_TIME]. Recent changes (deploys, config, traffic): [RECENT_CHANGES]. Monitoring and logs available: [OBSERVABILITY]. Impact on users: [USER_IMPACT]. What I already checked: [ALREADY_CHECKED]. STEPS: 1. Help me stabilize first: decide whether to roll back, disable a feature, or scale, with the criteria and the risks of each. 2. Build a hypothesis list ranked by likelihood and cost to test, using the symptoms and recent changes. 3. For each hypothesis give the exact check (query, log search, metric, command) and what each possible result means. 4. Guide communication: a status update template for stakeholders every 30 minutes. 5. After resolution, draft a blameless post-incident review with timeline, contributing factors, what went well, and action items with owners. OUTPUT FORMAT: Immediate actions, hypothesis table, checks, update template, and post-incident outline. QUALITY BAR: Prefer reversible actions and avoid changing multiple things at once. State what evidence would change your ranking. FOLLOW-UP: Ask me to paste the next piece of evidence after each check so we can adjust.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.