Skills › Engineering › Incident Post-Mortem Draft

Incident Post-Mortem Draft

Pull incident-related GitHub issues and commits, then generate a structured post-mortem document.

Superpowers: handler_dev · handler_generate

Requires connection: GitHub

When to use: An incident has been resolved and you need to write the post-mortem before the retrospective meeting.

Steps

Fetch the incident issue and linked PRs

Superpower: handler_dev — live API reference →

POST /v2/superpowers/handler_dev
{
  "action": "GITHUB_GET_ISSUE",
  "owner": "myorg",
  "repo": "myapp",
  "issue_number": 456
}

Use the GitHub issue number that tracked the incident.

Get comments and timeline from the issue

Superpower: handler_dev — live API reference →

POST /v2/superpowers/handler_dev
{
  "action": "GITHUB_LIST_ISSUE_COMMENTS",
  "owner": "myorg",
  "repo": "myapp",
  "issue_number": 456
}

Draft the post-mortem document

Superpower: handler_generate — live API reference →

POST /v2/superpowers/handler_generate
{
  "task": "chat",
  "prompt": "Write a blameless post-mortem for this incident. Sections: (1) Incident summary (2 sentences: what broke, when, impact), (2) Timeline (reconstruct from the comments — detection → investigation → fix → resolution), (3) Root cause, (4) Contributing factors, (5) Impact (users/services affected, duration), (6) What went well, (7) Action items (format: [Owner] → [Task] → [Due date]). Data: [steps 1-2]"
}

From previous step: issue (step 1) + comments/timeline (step 2) → inject

Outcome: Blameless post-mortem: timeline, root cause, impact, what went well, and action items.

Fetch this skill via API

GET /v2/skills/incident-post-mortem
Authorization: Bearer sk-hndlr-...