Back to catalog / Developer tools
Blameless postmortems and trackable actions
Use timelines and system conditions to explain incidents and assign owned, dated actions.
Skills
Collect alerts, logs, deployments, user impact, and recovery time promptly, then build a factual timeline. Focus on system conditions and failed detection/guardrails rather than blaming individuals; distinguish root and contributing factors with methods such as Five Whys. Give each action an owner, due date, impact, and completion check, then follow through; choose a full or quick template based on incident severity.
Permissions
Prerequisites
- Needs incident timeline, alert/log evidence, impact, and recovery data plus relevant participants.
Permissions
- May analyze approved incident evidence and draft a review/actions; publishing, assigning, or contacting people needs separate authorization.
Limitations
Findings depend on evidence quality; omit secrets and do not label unconfirmed hypotheses as root cause.
Pinned upstream source
- Repository
- wshobson/agents
- File path
- plugins/incident-response/skills/postmortem-writing/SKILL.md
- Pinned commit
46891e7e60da0e52baf1050b7b6391b64e84c6d9- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: MIT
Compatible tools
incident management platform · logs/metrics · Markdown docs
Main topic
Turn ecommerce campaign materials into a reviewable weekly brief