Release Incident Postmortem
Use when an incident has already been mitigated and the team needs a structured post-incident retrospective with timeline, impact, root cause, contributing factors, and follow-up actions.
Install
$ agentstack add skill-motao123-dev-workflow-kit-release-incident-postmortem ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-motao123-dev-workflow-kit-release-incident-postmortem) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Release Incident Postmortem
Use this skill when the incident is over and the focus is structured learning, not live triage.
Trigger Conditions
Use this skill when:
- an outage, regression, or release incident has already been mitigated
- the team needs a postmortem document with timeline and root-cause analysis
- follow-up actions, owners, and prevention work need to be captured
- a release-related incident requires a learning record beyond a chat summary
Do not use this skill while an incident is still active or when root cause is still unknown.
Workflow
- Confirm the incident is mitigated and stable.
- Reconstruct the timeline using available evidence.
- Summarize user-visible impact and scope.
- Identify root cause and contributing factors.
- Capture mitigation steps actually taken.
- Define concrete follow-up actions, owners, and verification.
Output
For non-trivial work, provide:
- timeline summary
- impact and scope
- root cause and contributing factors
- mitigation actions taken
- follow-up actions with owners
- recommended preventive changes
Coordination
After postmortem drafting:
- use
docs-writerto publish the postmortem and any external comms - use
release-rollout-strategyif rollout shape needs to change for prevention - use
systematic-debuggingonly if root cause turns out to still be unclear
Invocation Examples
- "Use release-incident-postmortem from dev-workflow-kit to run a structured postmortem on this outage."
- "Use release-incident-postmortem to capture timeline, impact, and follow-up actions for last night's incident."
- "Use release-incident-postmortem to write the retrospective doc now that mitigation is complete."
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: motao123
- Source: motao123/dev-workflow-kit
- License: MIT
- Homepage: https://motao123.github.io/dev-workflow-kit/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.