Incident postmortem qa checklist

Skill sisodiabhumca/agent-skills/skills/incident-postmortem-qa-checklist

Production-Ready Agent Skills : product analytics, growth experiments, CRM, research synthesis, postmortems, data contracts, SaaS spend, compliance, architecture maps, and LLM eval and many more.

Install

npx -y skills add sisodiabhumca/agent-skills --skill incident-postmortem-qa-checklist

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Vendor-neutral skill to turn an incident timeline into a postmortem QA checklist and identify missing or weak evidence.

SKILL.md

1.5 KB, as published. Nobody here has run it

When to invoke

After an outage or incident, to ensure the postmortem is complete and actionable.
During incident review, to highlight gaps in timeline, detection, impact, and follow-ups.

Inputs needed

Incident timeline as JSON events with timestamps and short descriptions.
Optional metadata: service name, severity, start/end time, customer impact.

Workflow

Validate timeline ordering and detect gaps (large time jumps, missing end time).
Classify events into phases: detection, triage, mitigation, recovery, follow-up.
Generate a checklist covering:
- Impact statement and affected users
- Detection signals and alerting
- Root cause evidence and contributing factors
- What worked / what didn’t
- Action items with owners and due dates
Flag common quality issues:
- No customer impact quantification
- No clear trigger/root cause evidence
- Action items missing owner or due date

Output format

JSON report:
- checks[] list (id, status, rationale)
- timeline_analysis (ordering, gaps)
- missing_evidence[]

Guardrails

Do not invent incident facts; only infer checklist gaps from provided inputs.
If timeline is too sparse, default to “needs more detail” statuses.

Reference code

incident_postmortem_qa_checklist.py reads timeline JSON and outputs checklist JSON.