postmortem-facilitator SKILL.md skillA
postmortem-facilitator from rizwanzafaris/product-manager-os is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add rizwanzafaris/product-manager-os/postmortem-facilitator@git:20260919.72235e0Pins git:20260919.72235e0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- rizwanzafaris/product-manager-os
- Path
skills/postmortem-facilitator/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260919.72235e0, committed Sep 19, 2026
- First version recorded
- Sep 3, 2026
- Size
- 9,935 bytes
- Repository stars
- 4
- License
- MIT
Facilitate a blameless incident postmortem: reconstruct the timeline from recorded sources, quantify impact, run five whys and a fishbone to reach causes the team can change, and leave with corrective actions that have owners, dates, and verification. Use when an incident qualifies for review under your severity policy, when a postmortem draft reads as a list of what people did wrong, when the same class of incident has recurred, or when a launch review found an operational failure it cannot…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Postmortem Facilitator: the same incident, made impossible A postmortem fails when it finds a person. The room learns that showing up to an incident earns a paragraph with your name in it, the next incident's responders hide what they saw, and the document starts collecting fiction. This skill runs the review so that every cause is something the team can change, every action has a verification a reviewer can check, and the responders leave wanting to be in the next room. ## Files this skill drives - [../../templates/operate/incident-postmortem.md](../../templates/operate/incident-postmortem.md), the document the review fills - [../../frameworks/execution/five-whys-fishbone.md](../../frameworks/execution/five-whys-fishbone.md), the two cause-analysis worksheets - [../../frameworks/systems/iceberg-model.md](../../frameworks/systems/iceberg-model.md), reached for when this class of incident has recurred after a fix already shipped. Five whys walks one chain back from one event; the iceberg pushes the event up to the pattern, the structure, and the belief that keep regenerating it, which is what you need when every chain arrives at a different person …
Read the whole file at its exact version.
How to install
mdr add rizwanzafaris/product-manager-os/postmortem-facilitator@sha256:7cfea3ee9caff7faThe line at the top of this page pins the label git:20260919.72235e0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_zprqgujtmo4x7cjp)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Sep 3, 2026 and Sep 19, 2026, about one every 8 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260919.72235e0 latest | 2026-09-19 | 72235e0 | 9,935 B | A | view · diff |
| git:20260903.fa79c16 | 2026-09-03 | fa79c16 | 8,240 B | A | view · diff |
| git:20260903.a2ef42e | 2026-09-03 | a2ef42e | 7,846 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9935 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
rizwanzafaris/product-manager-os · 4 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zprqgujtmo4x7cjp GET https://markdownregistry.com/api/v1/resolve?ref=rizwanzafaris/product-manager-os/postmortem-facilitator GET https://markdownregistry.com/api/v1/blob/7cfea3ee9caff7fac49e6b47331c7b16f633c576f6c4b1b1a81c06770427634b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.