AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Postmortem

skill-janellecipriano-pm-skills-postmortem · by janellecipriano

Run a blameless postmortem / incident review — timeline, impact, root cause analysis, and corrective actions. Use when the user says "postmortem", "incident review", "RCA", "root cause analysis", "what happened with the outage", or wants to turn an incident into a structured, blameless writeup with preventive actions.

No reviews yet
0 installs
44 views
0.0% view→install

Install

$ agentstack add skill-janellecipriano-pm-skills-postmortem

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

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

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-janellecipriano-pm-skills-postmortem)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

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 →
Are you the author of Postmortem? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Postmortem (Blameless Incident Review)

Turn an incident into learning and prevention — focused on systems and process, never on blaming individuals.

When to use

  • After an outage, regression, data issue, security event, or significant miss.

For sprint/project reflection (not incidents) use retrospective.

Principles

  • Blameless. Assume everyone acted reasonably with the information they had. Fix systems, not people. Replace "X made a mistake" with "the system allowed X to happen."
  • Facts first. Build the timeline from evidence (logs, alerts, messages) before drawing conclusions.
  • Root cause, not first cause. Use the 5 Whys / contributing-factors analysis to get past the proximate trigger.
  • Actions must prevent recurrence, be owned, and be dated.

Inputs to gather

  • What happened, when detected, when resolved; severity and who/what was impacted.
  • The timeline of events and the response.
  • Logs/notes if available.

Process

  1. Write a summary: what happened, impact (users/duration/scope), severity.
  2. Build a timeline (UTC or stated TZ): detection → diagnosis → mitigation → resolution. Note time-to-detect and time-to-resolve.
  3. Analyze root cause(s) and contributing factors (5 Whys).
  4. Note what went well and what made it worse (detection gaps, slow rollback, unclear ownership).
  5. Define corrective actions: preventive + detective, each with owner, due date, priority.
  6. Capture lessons learned.

Output format

# Postmortem — {{incident}} · {{date}}
**Severity:** {{SEV}} · **Impact:** {{users/scope/duration}} · **Status:** Resolved

## Summary
{{2–4 sentences}}

## Timeline
| Time | Event |

## Root cause & contributing factors
{{5 Whys / analysis}}

## What went well / what went poorly
- ...

## Action items
| Action | Type (prevent/detect) | Owner | Due | Priority |

Keep tone neutral and factual throughout.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.