Sync Upstream
nyaruka/phonenumbers
Sync this Go port with a new upstream google/libphonenumber release — regenerate the embedded metadata and reconcile the ported Java logic.
Judge a past decision by its PROCESS, not its outcome — because good decisions lose and bad decisions win, and teams that can't tell the difference learn the wrong lessons.
Install Decision Autopsy
$ npx skills add mohitagw15856/pm-claude-skills --skill decision-autopsy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills decision-autopsy --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/decision-autopsy .claude/skills/decision-autopsy && 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 "decision-autopsy" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/decision-autopsy into .claude/skills/decision-autopsy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "decision-autopsy", 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/decision-autopsyType 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 decision-autopsy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills decision-autopsy --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/decision-autopsy .agents/skills/decision-autopsy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "decision-autopsy" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/decision-autopsy into .agents/skills/decision-autopsy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "decision-autopsy", 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 decision-autopsy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills decision-autopsy --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/decision-autopsy .cursor/skills/decision-autopsy && 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 "decision-autopsy" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/decision-autopsy into .cursor/skills/decision-autopsy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "decision-autopsy", 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/decision-autopsy--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 decision-autopsy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills decision-autopsy --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/decision-autopsy .gemini/skills/decision-autopsy && 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 "decision-autopsy" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/decision-autopsy into .gemini/skills/decision-autopsy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "decision-autopsy", 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 decision-autopsyInstalls 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 decision-autopsy -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/decision-autopsy .github/skills/decision-autopsy && 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 "decision-autopsy" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/decision-autopsy into .github/skills/decision-autopsy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "decision-autopsy", 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 decision-autopsy -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 decision-autopsy --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/decision-autopsy .opencode/skills/decision-autopsy && 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 "decision-autopsy" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/decision-autopsy into .opencode/skills/decision-autopsy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "decision-autopsy", 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
decision-autopsy- GitHub stars
- 1.4k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 595 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Judge a past decision by its PROCESS, not its outcome — because good decisions lose and bad decisions win, and teams that can't tell the difference learn the wrong lessons.
- Works in 5 steps: The two verdicts, separated — Decision:… → The knowability ledger — table: fact |… → The luck accounting — one honest… → …
- Reviewing a big call after the fact (a bet that failed
- SKILL.md covers Required Inputs, The Forensic Frames, Output Format and Quality Checks, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Decision Autopsy is an agent skill from mohitagw15856/pm-claude-skills. Judge a past decision by its PROCESS, not its outcome — because good decisions lose and bad decisions win, and teams that can't tell the difference learn the wrong lessons. Use when reviewing a big call after the fact (a bet that failed, a pass that haunts, a hire, a pivot) and the room is about to conclude 'it failed so it was wrong.' Produces a process-forensics report: what was knowable then, the quality grade of the decision as-made, the luck accounting, and the ONE process change worth keeping.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Business, Finance & HR, covering Accounting and bookkeeping. 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
- Reviewing a big call after the fact (a bet that failed
- A pass that haunts
- A pivot) and the room is about to conclude it failed so it was wrong. Produces a process-forensics report: what was knowable then
- The quality grade of the decision as-made
Example prompts
- “it failed so it was wrong.”
- “/decision-autopsy”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- The two verdicts, separated — Decision: 🟢 sound / 🟡 flawed / 🔴 negligent as made. Outcome: good / bad / mixed. State them side by side…
- The knowability ledger — table: fact | knowable then? | actually known? | changed the call? Hindsight contamination gets flagged…
- The luck accounting — one honest paragraph: what fraction of this outcome was variance, with the reasoning shown.
- The one process change — a single, named, repeatable change to how decisions like this get made ("every >$100k bet gets a written…
- The replay line — "facing the same information again, the right call would be ___" — the sentence that inoculates the team against both…
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
Decision Autopsy loads about 1.1k tokens when it runs. Until then it costs about 130 tokens; SKILL.md has 595 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). 595 words, ~1,113 tokens.
Download SKILL.mdSave it as
.claude/skills/decision-autopsy/SKILL.md (or your agent's skills folder).- name
- decision-autopsy
- description
- Judge a past decision by its PROCESS, not its outcome — because good decisions lose and bad decisions win, and teams that can't tell the difference learn the wrong lessons. Use when reviewing a big call after the fact (a bet that failed, a pass that haunts, a hire, a pivot) and the room is about to conclude 'it failed so it was wrong.' Produces a process-forensics report: what was knowable then, the quality grade of the decision as-made, the luck accounting, and the ONE process change worth keeping.
Decision Autopsy
Outcome bias is the strongest bias in organisational memory: the bet that failed becomes "obviously reckless," the coin-flip that landed becomes "visionary." The autopsy separates the two questions that always get merged: was it a good decision? and did it get a good outcome? — because only the first is under anyone's control next time.
Required Inputs
- The decision — what was decided, when, by whom, and what the live alternatives were.
- What was knowable at the time — the information, constraints, and time pressure as of the decision date. Be strict: things learned afterward go in a separate pile, and the autopsy will police the boundary.
- The outcome — what actually happened, so the luck accounting has something to account.
The Forensic Frames
- The information test: given only what was knowable then, what would a calibrated outsider have chosen? (The autopsy answers this before re-examining the outcome, to keep hindsight out of the grade.)
- The process test: were alternatives really generated? Was disconfirming evidence sought or only tolerated? Was the reversibility of the choice priced in? Was a kill-criterion set?
- The luck accounting: decompose the outcome into decision quality vs. variance — what portion of the result would replay differently if the world rolled again?
- The lesson filter: the only lessons worth keeping are process lessons ("we never priced reversibility") — outcome lessons ("don't bet on X") overfit to one roll of the dice.
Output Format
- The two verdicts, separated — Decision: 🟢 sound / 🟡 flawed / 🔴 negligent as made. Outcome: good / bad / mixed. State them side by side; the whole point is that they can disagree.
- The knowability ledger — table: fact | knowable then? | actually known? | changed the call? Hindsight contamination gets flagged explicitly ("this entered the story after the fact").
- The luck accounting — one honest paragraph: what fraction of this outcome was variance, with the reasoning shown.
- The one process change — a single, named, repeatable change to how decisions like this get made ("every >$100k bet gets a written kill-criterion before commitment"). One. Teams adopt one; they file lists.
- The replay line — "facing the same information again, the right call would be ___" — the sentence that inoculates the team against both regret and false confidence.
Show full SKILL.md (232 more words)Show less
Quality Checks
- The decision grade was assigned from the knowability ledger BEFORE outcome discussion, and the report's structure shows it
- At least one hindsight contamination is caught and named — reviews without any are usually not looking
- The luck paragraph commits to a rough proportion, with reasoning — "some luck was involved" is evasion
- The process change is executable next quarter and testable ("did we do it?"), not a value statement
- If the decision was 🟢 and the outcome bad, the report says the uncomfortable sentence plainly: "do it again"
Anti-Patterns
- Do not let the outcome leak into the grade — a bad result may not appear as evidence of a bad decision anywhere in the report
- Do not run an autopsy as a trial — no verdicts on people; the unit of analysis is the process that any competent person was embedded in
- Do not conclude "we were unlucky" without the ledger to earn it — luck is the residual after process is examined, never the headline
- Do not extract more than one lesson — the second-best lesson dilutes the best one
- Do not autopsy decisions younger than their outcome — if the result isn't actually in yet, this is a premortem's job
Example Trigger Phrases
- "Was this a bad decision or just bad luck?"
- "Review the call we made last year."
- "Judge this decision by its process, not the outcome."
- "What should we learn from this failed bet?"
© 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/decision-autopsy of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Decision Autopsy 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 |
|---|---|---|---|---|---|---|
| Decision Autopsy this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Sync Upstreamnyaruka/phonenumbers | 1.6k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Radiology Tablehuang-sir1/radiology-skills | 1.9k | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| ERPClaw ERP Controlleravansaber/erpclaw | 116 | — | ~18k | Automated safety check: Pass | GPL-3.0 | |
| Odoo Agency Fleet Reviewerpipe-org/mcp-odoo | 421 | — | ~699 | Automated safety check: Pass | MIT | |
| Beancount Closebex-co/beancount-io | 297 | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Radiology Table
huang-sir1/radiology-skills
Create/audit editable publication tables with source reconciliation; not figures or statistical inference.
ERPClaw ERP Controller
avansaber/erpclaw
Operates the ERPClaw self-hosted ERP in plain language: accounting, invoicing, inventory, purchasing, tax, HR, payroll and reports, treating the ERP as the single source of truth.
Odoo Agency Fleet Review
erpipe-org/mcp-odoo
Review many client Odoo databases at once through odoo-mcp's cross-instance tools — fleet-wide accounting health, per-client aging, partial-failure triage — for agencies and partners managing 5–50…
Beancount Close
bex-co/beancount-io
Close an accounting period in a Beancount ledger by reconciling each active account through beancount-reconcile, checking assertions and recurring gaps, reviewing flags, then proposing a commit with…
Forward Implementation First
Vuk97/forward-implementation-first
Keeps an agent building and validating real output instead of servicing its own bookkeeping.
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.
Related
Categories
Questions about Decision Autopsy
What does Decision Autopsy do?
Judge a past decision by its PROCESS, not its outcome — because good decisions lose and bad decisions win, and teams that can't tell the difference learn the wrong lessons. Decision Autopsy is an agent skill from mohitagw15856/pm-claude-skills. Judge a past decision by its PROCESS, not its outcome — because good decisions lose and bad decisions win, and teams that can't tell the difference learn the wrong lessons.
When should I use Decision Autopsy?
Decision Autopsy fits situations like: reviewing a big call after the fact (a bet that failed; A pass that haunts; A pivot) and the room is about to conclude it failed so it was wrong. Produces a process-forensics report: what was knowable then; the quality grade of the decision as-made.
How do I install Decision Autopsy in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill decision-autopsy -a claude-code`. Or copy the skill folder (skills/decision-autopsy in mohitagw15856/pm-claude-skills) into .claude/skills/decision-autopsy in your project. Claude Code loads it when a task matches its description.
How do I install Decision Autopsy in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill decision-autopsy -a codex`. Or copy the skill folder (skills/decision-autopsy in mohitagw15856/pm-claude-skills) into .agents/skills/decision-autopsy in your project. Codex loads it when a task matches its description.
Can I use Decision Autopsy 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 decision-autopsy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/decision-autopsy, .gemini/skills/decision-autopsy, .github/skills/decision-autopsy and .opencode/skills/decision-autopsy in your project.
What does Decision Autopsy need to run?
SKILL.md names no scripts, command-line tools or credentials: Decision Autopsy is instructions for the agent only.
Does Decision Autopsy 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 Decision Autopsy 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 Decision Autopsy use?
Decision Autopsy 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 Decision Autopsy use?
About 1.1k tokens (SKILL.md is roughly 4.5k 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 Decision Autopsy?
Skills that share tags, products or a category with Decision Autopsy: Sync Upstream (nyaruka/phonenumbers, 1.6k stars), Radiology Table (huang-sir1/radiology-skills, 1.9k stars), ERPClaw ERP Controller (avansaber/erpclaw, 116 stars) and Odoo Agency Fleet Review (erpipe-org/mcp-odoo, 421 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Decision Autopsy?
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.