Set up
Try a plugin
The Engineering plugin ships with /incident-response and other incident-and-ops skills as a starting point, already structured to write a blameless postmortem with a timestamped timeline. If your admin manages plugins and it's not available yet, skip this step. The prompt below works without it.
/incident-responseRun an incident response workflow — triage, communicate, and write postmortem./standupGenerate a standup update from recent activity.Connect your tools
Claude is more powerful when it works directly with your systems. You control permissions and access. Learn about tool access(opens in new tab).
Add a connector(opens in new tab) for each tool you want Claude to use.
Set your working folder
Drag the files you'll use (your postmortem template, the runbook, any log exports or graph screenshots) into one folder and give Claude access to it(opens in new tab) in the Claude desktop app. Claude reads the template from there and writes the draft back to it. Create a project(opens in new tab) from your incidents folder so your template, severity definitions, and blameless-language guide stay attached.
The prompt
Copy this into Claude
From #inc-2026-04-22-checkout-5xx, reconstruct the sequence of events with timestamps, write the customer impact summary, identify the root cause and contributing factors, and draft the postmortem in our template with owners on every action item. Be blameless: describe what the system did, not who made a mistake.
Why this works
Reconstruct, don't summarize. Asking for the timestamped sequence means the timeline is built from evidence, not memory.
Separate root cause from contributing factors. Forces a real causal chain instead of a single scapegoat line.
State the tone you want. Language stays on system behavior; the doc survives review.
Provide your template as context. Output drops straight into your sections, your severity scale, your action-item format.
Get a better draft
Add an example to match. Drop an example you like into the folder and Claude matches your structure and voice.
Ask it to flag uncertainty. Add "flag anything you're not confident about" so you know where to look first when you review the draft.
Make Claude work for you
Tell Claude your team's standards for postmortems, such as your severity definitions and your blameless-language rules, then save what you've done as a skill of your own. A few minutes of conversation and it runs with your standards from then on.
Make what we've done in this task so far into a skill called /postmortem-draft.
Review the skill, and save it if Claude hasn't already.
Make it repeatable
Run it when the incident closes
The draft should exist before the review meeting is scheduled. Ask Claude to set up a scheduled task, or open Scheduled in the sidebar, and /postmortem-draft runs on each resolved incident and writes the first draft into the matching folder.
Set up a scheduled task for every weekday at 6pm: check PagerDuty for incidents resolved since the last run, run /postmortem-draft on each one, and write the draft to Incidents/<incident-folder>/postmortem-draft.md.
Every weekday at 6pm, finds incidents resolved since the last run, runs /postmortem-draft against the channel and timeline, and writes the draft to the incident folder.
To use a folder on your computer during a scheduled task, keep your computer on and awake with the Claude desktop app open so Claude can access it.
Share with your teammates
Your /postmortem-draft skill now carries your template, your severity definitions, and your blameless-language rules. Share it so every on-call engineer writes the doc the same way, and the review meeting starts at "is this right" instead of "who's writing this up."