# 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.

- **Type:** Skill
- **Install:** `agentstack add skill-motao123-dev-workflow-kit-release-incident-postmortem`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [motao123](https://agentstack.voostack.com/s/motao123)
- **Installs:** 0
- **Category:** [Cloud & Infrastructure](https://agentstack.voostack.com/c/cloud-infrastructure)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [motao123](https://github.com/motao123)
- **Source:** https://github.com/motao123/dev-workflow-kit/tree/main/release-incident-postmortem
- **Website:** https://motao123.github.io/dev-workflow-kit/

## Install

```sh
agentstack add skill-motao123-dev-workflow-kit-release-incident-postmortem
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## 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

1. Confirm the incident is mitigated and stable.
2. Reconstruct the timeline using available evidence.
3. Summarize user-visible impact and scope.
4. Identify root cause and contributing factors.
5. Capture mitigation steps actually taken.
6. 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-writer` to publish the postmortem and any external comms
- use `release-rollout-strategy` if rollout shape needs to change for prevention
- use `systematic-debugging` only 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](https://github.com/motao123)
- **Source:** [motao123/dev-workflow-kit](https://github.com/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.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-motao123-dev-workflow-kit-release-incident-postmortem
- Seller: https://agentstack.voostack.com/s/motao123
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.
