Post Mortem
alirezarezvani/claude-skills
/cs:post-mortem <decision — Honest retrospective on an executed decision, scored against original assumptions and dissent.
Imagine your plan already failed, then get five independent 'here's why it died' stories — before you commit.
MITAuto-check passed
Install Pre Mortem Panel
$ npx skills add mohitagw15856/pm-claude-skills --skill pre-mortem-panel -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills pre-mortem-panel --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pre-mortem-panel .claude/skills/pre-mortem-panel && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pre-mortem-panel" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/pre-mortem-panel into .claude/skills/pre-mortem-panel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-mortem-panel", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/pre-mortem-panelType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill pre-mortem-panel -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills pre-mortem-panel --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/pre-mortem-panel .agents/skills/pre-mortem-panel && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pre-mortem-panel" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/pre-mortem-panel into .agents/skills/pre-mortem-panel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-mortem-panel", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill pre-mortem-panel -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills pre-mortem-panel --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/pre-mortem-panel .cursor/skills/pre-mortem-panel && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pre-mortem-panel" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/pre-mortem-panel into .cursor/skills/pre-mortem-panel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-mortem-panel", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/pre-mortem-panel--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill pre-mortem-panel -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills pre-mortem-panel --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/pre-mortem-panel .gemini/skills/pre-mortem-panel && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pre-mortem-panel" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/pre-mortem-panel into .gemini/skills/pre-mortem-panel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-mortem-panel", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills pre-mortem-panelInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill pre-mortem-panel -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/pre-mortem-panel .github/skills/pre-mortem-panel && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pre-mortem-panel" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/pre-mortem-panel into .github/skills/pre-mortem-panel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-mortem-panel", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill pre-mortem-panel -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills pre-mortem-panel --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/pre-mortem-panel .opencode/skills/pre-mortem-panel && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pre-mortem-panel" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/pre-mortem-panel into .opencode/skills/pre-mortem-panel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-mortem-panel", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pre-mortem-panel- GitHub stars
- 1.4k
- Token cost
- ~936 tokens
- SKILL.md length
- 458 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Imagine your plan already failed, then get five independent 'here's why it died' stories — before you commit.
- Works in 5 steps: Jump to the failure. Assume the plan has… → Diversify the causes. Run five… → Rank likely vs. lethal. Separate the… → …
- Asked to pre-mortem this
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: Assume It Failed,… and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Pre Mortem Panel is an agent skill from mohitagw15856/pm-claude-skills. Imagine your plan already failed, then get five independent 'here's why it died' stories — before you commit. Use when asked to pre-mortem this, why might this fail, what are the risks before I start, or imagine this went wrong. Produces five distinct failure narratives (each from a different cause — execution, timing, people, external, wrong-assumption), the most likely and most lethal among them, the early warning signs of each, and the specific mitigations worth doing now — catching failures while they're…
Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to pre-mortem this
- Why might this fail
- What are the risks before I start
- Imagine this went wrong
Example prompts
- “s why it died”
- “/pre-mortem-panel”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Jump to the failure. Assume the plan has already failed — this concreteness surfaces risks that abstract risk-listing misses.
- Diversify the causes. Run five independent stories from genuinely different roots so you cover the whole failure surface, not one fear…
- Rank likely vs. lethal. Separate the most probable failure from the most damaging — plan for both, but differently.
- Find the early signals. For the top failures, name the leading indicators you'd actually see, so you can react before it's terminal.
- Mitigate now. Turn the top risks into specific actions worth taking before you start, prioritized by leverage.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Pre Mortem Panel loads about 936 tokens when it runs. Until then it costs about 139 tokens; SKILL.md has 458 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 458 words, ~936 tokens.
Download SKILL.mdSave it as
.claude/skills/pre-mortem-panel/SKILL.md (or your agent's skills folder).- name
- pre-mortem-panel
- description
- Imagine your plan already failed, then get five independent 'here's why it died' stories — before you commit. Use when asked to pre-mortem this, why might this fail, what are the risks before I start, or imagine this went wrong. Produces five distinct failure narratives (each from a different cause — execution, timing, people, external, wrong-assumption), the most likely and most lethal among them, the early warning signs of each, and the specific mitigations worth doing now — catching failures while they're still cheap to prevent.
Pre-Mortem Panel
A pre-mortem beats a risk list because it's concrete: you assume the failure already happened and explain it, which surfaces problems a bland "what are the risks?" never does. This runs five independent pre-mortems from different causes, so you don't just get five versions of the same fear — you get the full failure surface, ranked, with the warning signs and the fixes worth doing before you start.
What This Skill Produces
- Five failure stories — each a vivid "it's six months later and this failed because…" from a different root cause (execution, timing/market, people, external shock, a wrong core assumption)
- Most likely vs. most lethal — which failure is most probable and which would hurt most (they're often different)
- Early warning signs — the signals that each failure is starting to happen, so you can catch it live
- Mitigations worth doing now — the specific, prioritized moves to prevent or de-risk the top failures
Required Inputs
Ask for these if not provided:
- The plan or project — what you're about to commit to
- The timeframe — when "did it work?" gets answered
- What's at stake — so we prioritize lethal vs. minor failures
- Known worries — anything already nagging you
Framework: Assume It Failed, From Five Angles
- Jump to the failure. Assume the plan has already failed — this concreteness surfaces risks that abstract risk-listing misses.
- Diversify the causes. Run five independent stories from genuinely different roots so you cover the whole failure surface, not one fear five times.
- Rank likely vs. lethal. Separate the most probable failure from the most damaging — plan for both, but differently.
- Find the early signals. For the top failures, name the leading indicators you'd actually see, so you can react before it's terminal.
- Mitigate now. Turn the top risks into specific actions worth taking before you start, prioritized by leverage.
Show full SKILL.md (154 more words)Show less
Output Format
Pre-mortem: [the plan] · by [timeframe]
Five ways it died
- Execution: [story]. 2. Timing/market: [story]. 3. People: [story]. 4. External: [story]. 5. Wrong assumption: [story].
Most likely: [x]. Most lethal: [y]. Early warning signs: [signal → which failure it means]. Do now to de-risk: [prioritized mitigations].
Quality Checks
- Five failure stories from genuinely different root causes
- They're concrete narratives, not a vague risk list
- Most-likely and most-lethal are distinguished
- Early warning signs are named for the top failures
- Specific, prioritized mitigations are proposed
Anti-Patterns
- One fear repeated five times.
- Abstract risks ("competition") instead of concrete stories.
- Treating likely and lethal as the same.
- Warnings with no mitigations to act on.
Example Trigger Phrases
- "Pre-mortem my product launch."
- "Imagine my trip / event / project went wrong — why?"
- "What are the ways this could fail before I commit?"
- "Run a pre-mortem on my career move."
- "Five reasons this plan might die, and how to prevent them."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/pre-mortem-panel of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Pre Mortem Panel next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pre Mortem Panel this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~936 | Automated safety check: Pass | MIT | |
| Post Mortemalirezarezvani/claude-skills | 28k | — | ~968 | Automated safety check: Pass | MIT | |
| Pre Mortemphuryn/pm-skills | 27k | — | ~1k | Automated safety check: Pass | MIT | |
| Debug Failed Runactivepieces/activepieces | 25k | — | ~3.7k | Automated safety check: Warn | Custom licence | |
| Porters Five Forcesphuryn/pm-skills | 27k | — | ~2k | Automated safety check: Pass | MIT | |
| Fix Failing Pipelinesa5c-ai/babysitter | 1.8k | — | ~1k | Automated safety check: Pass | MIT |
Similar skills
Pre Mortem
phuryn/pm-skills
Run a pre-mortem risk analysis on a PRD or launch plan. An agent skill from phuryn/pm-skills.
Debug Failed Run
activepieces/activepieces
Debug a failed Activepieces flow run end-to-end: given a flow run id (or BullMQ job id), find why it failed, cross-referencing the live BullMQ job + Postgres rows (SSH script on the DevOps box), the…
Porters Five Forces
phuryn/pm-skills
Perform Porter's Five Forces analysis — competitive rivalry, supplier power, buyer power, threat of substitutes, and threat of new entrants.
Fix Failing Pipelines
a5c-ai/babysitter
This skill should be used when the user asks to "fix pipelines", "fix CI", "check staging pipelines", "fix failing workflows", "fix failing actions", or wants to find and fix failing GitHub Actions…
Recipe Post Mortem Setup
googleworkspace/cli
Create a Google Docs post-mortem, schedule a Google Calendar review, and notify via Chat.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Questions about Pre Mortem Panel
What does Pre Mortem Panel do?
Imagine your plan already failed, then get five independent 'here's why it died' stories — before you commit. Pre Mortem Panel is an agent skill from mohitagw15856/pm-claude-skills. Imagine your plan already failed, then get five independent 'here's why it died' stories — before you commit.
When should I use Pre Mortem Panel?
Pre Mortem Panel fits situations like: asked to pre-mortem this; why might this fail; what are the risks before I start; imagine this went wrong.
How do I install Pre Mortem Panel in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill pre-mortem-panel -a claude-code`. Or copy the skill folder (skills/pre-mortem-panel in mohitagw15856/pm-claude-skills) into .claude/skills/pre-mortem-panel in your project. Claude Code loads it when a task matches its description.
How do I install Pre Mortem Panel in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill pre-mortem-panel -a codex`. Or copy the skill folder (skills/pre-mortem-panel in mohitagw15856/pm-claude-skills) into .agents/skills/pre-mortem-panel in your project. Codex loads it when a task matches its description.
Can I use Pre Mortem Panel in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill pre-mortem-panel -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pre-mortem-panel, .gemini/skills/pre-mortem-panel, .github/skills/pre-mortem-panel and .opencode/skills/pre-mortem-panel in your project.
What does Pre Mortem Panel need to run?
SKILL.md names no scripts, command-line tools or credentials: Pre Mortem Panel is instructions for the agent only.
Does Pre Mortem Panel access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Pre Mortem Panel safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Pre Mortem Panel use?
Pre Mortem Panel is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Pre Mortem Panel use?
About 936 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Pre Mortem Panel?
Skills that share tags, products or a category with Pre Mortem Panel: Post Mortem (alirezarezvani/claude-skills, 28k stars), Pre Mortem (phuryn/pm-skills, 27k stars), Debug Failed Run (activepieces/activepieces, 25k stars) and Porters Five Forces (phuryn/pm-skills, 27k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pre Mortem Panel?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.