What is the Incident Post-Mortem Facilitator prompt?

The Incident Post-Mortem Facilitator prompt is a professionally crafted AI prompt template designed for Claude Sonnet 3.5 to help you incident post-mortem facilitator. It's optimized for Engineering use cases and includes customizable variables for personalization.

How do I use the Incident Post-Mortem Facilitator prompt?

To use this prompt: 1) Copy the prompt text using the copy button, 2) Customize any variables in brackets like [YOUR_INPUT] with your specific details, 3) Paste into Claude Sonnet 3.5, and 4) Review and iterate on the output as needed.

Is the Incident Post-Mortem Facilitator prompt free to use?

Yes, all prompts on VePrompts are completely free to use for personal and commercial purposes. You can copy, customize, and use them as many times as you need without any restrictions or attribution requirements.

Does the Incident Post-Mortem Facilitator prompt work with other AI models?

While optimized for Claude Sonnet 3.5, this prompt is designed to work with most major AI models including ChatGPT, Claude, Gemini, and others. You may need to make minor adjustments for optimal results with different models.

Claude Sonnet 3.5 Engineering

While optimized for Claude Sonnet 3.5, this prompt is compatible with most major AI models.

Incident Post-Mortem Facilitator

Facilitate a blameless post-mortem (RCA) to analyze a recent incident, identify root causes, and generate action items to prevent recurrence.

Prompt Health: 100%

Length

Structure

Variables

Est. 301 tokens

# Role You are a Site Reliability Engineer (SRE) and Incident Commander. You practice "Blameless Post-Mortems" focusing on process and technology improvements rather than human error. # Task Draft an Incident Post-Mortem report based on the raw timeline and details provided. **Incident Details:** - **Incident Date:** [YYYY-MM-DD] - **Impact:** [Who was affected? How long? Severity?] - **Timeline/Events:** ``` [PASTE_ROUGH_TIMELINE_OR_CHAT_LOGS] ``` - **Root Cause (if known):** [Brief description] - **Resolution:** [How was it fixed?] # Instructions 1. **Executive Summary**: Write a high-level overview for leadership. 2. **Timeline**: Clean up the provided timeline into a clear chronological sequence. 3. **5 Whys Analysis**: Perform a "5 Whys" analysis to drill down to the true root cause. (e.g., Server crashed -> Out of memory -> Memory leak -> Unbounded cache -> Code review missed strict limit). 4. **Action Items**: Suggest specific, preventive action items (not just "be more careful"). Categories: - **Detect**: How to catch this faster next time? - **Prevent**: How to stop this from happening? - **Mitigate**: How to reduce impact if it happens again?

Source