debug-postmortem
Domain: debug · Model class: cheap
Description
Section titled “Description”Use this skill when the user wants to work on Generating structured postmortems with timelines, root causes, impact, and action items. Triggers include “generate a postmortem”, “write an incident report”, “summarize this incident”. Do NOT use when triage the incident first (use core-debugging-assistant).
Purpose
Section titled “Purpose”Generating structured postmortems with timelines, root causes, impact, and action items. This skill provides structured guidance, references, and worked examples to help produce high-quality, actionable outputs.
Trigger Phrases
Section titled “Trigger Phrases”- “generate a postmortem”
- “write an incident report”
- “summarize this incident”
- “extract action items from this outage”
Anti-Triggers
Section titled “Anti-Triggers”- triage the incident first (use core-debugging-assistant)
- create a runbook to prevent recurrence (use core-runbook-generator)
Intake Questions
Section titled “Intake Questions”- What is the user’s goal and current state?
- What constraints (time, team, compliance) apply?
- Are there existing artifacts (specs, code, benchmarks) to reference?
Output Contract
Section titled “Output Contract”- structured response
- actionable steps
- context-aware recommendations
- clear handoff or validation guidance