Write a blameless post-mortem.
INCIDENT: {what_broke}
WHEN: {date_and_time_window}
IMPACT: {users_affected, revenue_loss, SLA_breach}
WHO RESPONDED: {team / on-call}
FORMAT:
- **Summary** (3 sentences a non-engineer can follow)
- **Timeline** (UTC timestamps, every detection / mitigation / decision — not feelings)
- **Root cause** (the technical cause AND the system-level cause; eg. 'we deployed at 3pm on a Friday' is system, not technical)
- **Trigger** (the specific change that lit the fuse)
- **Resolution** (what stopped the bleeding)
- **What went well** (3 things — celebrate the saves)
- **What didn't go well** (3 things — never blaming a person, always a system)
- **Action items** (Owner | Action | Due date | Type: prevention / detection / response)
- **Where we got lucky** (the bullets that could have made it much worse)
Use no names of individuals. Use roles ('on-call eng', 'release manager').0 copies·0 saves·9 views
142 words·917 chars
Parameters
Text generation parameters
FAQ
A coding & development text prompt designed for Claude Sonnet. 142 words long, free to copy and use.
This prompt is written for Claude Sonnet. It's a text/chat prompt — paste it into Claude Sonnet (or compatible LLMs like Claude or GPT-4) to get the expected output.
1. Click the Copy button on this page to copy the full prompt. 2. Open Claude Sonnet. 3. Paste the prompt into a new conversation. 4. Replace any {placeholders} with your specifics, then send. Most prompts produce the right output on the first try; complex ones may need 1-2 iterations.
Yes — every prompt on mycopyprompt is free forever. No paywall, no signup wall for browsing or copying. You can use it for personal or commercial work, just don't redistribute the entire mycopyprompt library.
Absolutely — most prompts are templates. Look for {placeholders} (curly braces) and swap them with your own values. You can also reword sections, add constraints, or chain it with other prompts.
Similar prompts
Matched against every prompt in the catalog by title.