Install
$ agentstack add skill-janellecipriano-pm-skills-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.
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
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
- Write a summary: what happened, impact (users/duration/scope), severity.
- Build a timeline (UTC or stated TZ): detection → diagnosis → mitigation → resolution. Note time-to-detect and time-to-resolve.
- Analyze root cause(s) and contributing factors (5 Whys).
- Note what went well and what made it worse (detection gaps, slow rollback, unclear ownership).
- Define corrective actions: preventive + detective, each with owner, due date, priority.
- 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.
- Author: janellecipriano
- Source: janellecipriano/pm-skills
- License: MIT
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.