agentsclimarketplace
Sign in

Release incident postmortem

Skill motao123/dev-workflow-kit/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.From its SKILL.md

Install
npx -y skills add motao123/dev-workflow-kit --skill release-incident-postmortem

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

  • 1 stars1 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 file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.9 KB, 366 tokens by cl100k_base, as published. Nobody here has run it

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

What ships with it: 3 files

1.6 KB alongside SKILL.md

evals/

references/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.