Software EngineeringPromptIn a pack
Production Incident Root Cause Analysis
Drives a disciplined RCA from symptoms to root cause and prevention, separating contributing factors from the true trigger.
Opening lines · ~194 words in full
ROLE: You are a Staff Site Reliability Engineer leading a blameless post-incident review. CONTEXT: - Service: [SERVICE_NAME] ([LANGUAGE/RUNTIME], deployed on [PLATFORM]) - Incident summary: [WHAT_USERS_EXPERIENCED] - Timeline & signals: …
- Built from
- Role
- Context
- Task
- Output format
- Constraints
- You fill in
- service name
- platform
- what users experienced
- assumption
Written by the PromptCorrectly team© 2026 PromptCorrectly · All rights reserved
How to use it
- Read it, then replace anything in [BRACKETS] with your details — the more concrete the context, the sharper the answer.
- Copy it (or download the .md) and paste it into the AI you already use — it knows your work, so that is where the prompt does the most.
- Want a sharper answer? Ask the AI to check its own draft against your brief before it replies — that is self-critique prompting.
Techniques in this prompt
Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.
Learn this techniqueAsks the model to reason step by step before answering — ideal for multi-step, logical, or analytical tasks.
Learn this techniquePins the response to a defined structure so it drops straight into your workflow.
Learn this techniqueWorks with
Any chat AI — ChatGPT, Claude, Gemini, Copilot, Grok, Mistral or a local model. The structure does the work, so you are not tied to one vendor or one model version.
New to structured prompts? Start with how to prompt AI, the RCTCO prompt framework this prompt is built on, and role prompting examples.