Premortem
parcadei/Continuous-Claude-v3
Identify failure modes before they occur using structured risk analysis
Pre-mortem analysis that imagines a plan has failed, then works backward to identify causes and preventions.
MITAuto-check passed
Install Premortem
$ npx skills add neurofoo/agent-skills --skill premortem -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install neurofoo/agent-skills premortem --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/neurofoo/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/premortem .claude/skills/premortem && 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 "premortem" agent skill from https://github.com/neurofoo/agent-skills/tree/main/premortem into .claude/skills/premortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "premortem", 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/neurofoo/agent-skills/tree/main/premortemType 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 neurofoo/agent-skills --skill premortem -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install neurofoo/agent-skills premortem --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/premortem .agents/skills/premortem && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "premortem" agent skill from https://github.com/neurofoo/agent-skills/tree/main/premortem into .agents/skills/premortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "premortem", 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 neurofoo/agent-skills --skill premortem -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install neurofoo/agent-skills premortem --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/premortem .cursor/skills/premortem && 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 "premortem" agent skill from https://github.com/neurofoo/agent-skills/tree/main/premortem into .cursor/skills/premortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "premortem", 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/neurofoo/agent-skills.git --path premortem--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 neurofoo/agent-skills --skill premortem -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install neurofoo/agent-skills premortem --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/premortem .gemini/skills/premortem && 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 "premortem" agent skill from https://github.com/neurofoo/agent-skills/tree/main/premortem into .gemini/skills/premortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "premortem", 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 neurofoo/agent-skills premortemInstalls 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 neurofoo/agent-skills --skill premortem -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/premortem .github/skills/premortem && 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 "premortem" agent skill from https://github.com/neurofoo/agent-skills/tree/main/premortem into .github/skills/premortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "premortem", 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 neurofoo/agent-skills --skill premortem -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install neurofoo/agent-skills premortem --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/premortem .opencode/skills/premortem && 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 "premortem" agent skill from https://github.com/neurofoo/agent-skills/tree/main/premortem into .opencode/skills/premortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "premortem", 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
premortem- GitHub stars
- 119
- Used in
- 3 other repos
- Token cost
- ~568 tokens
- SKILL.md length
- 254 words
- Files
- 1
- Skills in repo
- 22
- Repo updated
- First seen
- Licence
- MIT
At a glance
Pre-mortem analysis that imagines a plan has failed, then works backward to identify causes and preventions.
- SKILL.md covers Instructions and Guidelines
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Premortem is an agent skill from neurofoo/agent-skills. Pre-mortem analysis that imagines a plan has failed, then works backward to identify causes and preventions. Use before launches, major decisions, or risky initiatives to surface hidden risks.
Its SKILL.md is about 570 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: Agent Skills for Claude Code and OpenCode. The licence is MIT.
Example prompts
- “/premortem”
What it can do on your machine
Read from SKILL.md and the folder at commit 0e7ac2a. 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
Premortem loads about 568 tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 254 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 neurofoo/agent-skills at commit 0e7ac2a, republished under its MIT licence (© neurofoo). 254 words, ~568 tokens.
Download SKILL.mdSave it as
.claude/skills/premortem/SKILL.md (or your agent's skills folder).- name
- premortem
- description
- Pre-mortem analysis that imagines a plan has failed, then works backward to identify causes and preventions. Use before launches, major decisions, or risky initiatives to surface hidden risks.
- user-invocable
- true
Pre-Mortem Analysis
Imagine the plan has completely failed, then work backward to identify what went wrong and how to prevent it.
Instructions
Set the scene: "It's [timeframe] in the future. This initiative was a complete disaster. Looking back, what happened?"
Generate failure scenarios without filtering for likelihood—get everything on the table first, then prioritize.
Output Format
The Plan Summarize what's being attempted and the success criteria.
Time Jump "It's [X months] later. This has failed completely. The outcome: [describe the disaster vividly]."
What Went Wrong
Generate 8-12 plausible failure causes across categories:
| Category | Failure Mode | How It Played Out |
|---|---|---|
| Execution | [What failed] | [The story of how] |
| External | [What failed] | [The story of how] |
| People | [What failed] | [The story of how] |
| Technical | [What failed] | [The story of how] |
| Assumptions | [What failed] | [The story of how] |
Risk Prioritization
| Failure Mode | Likelihood | Impact | Priority |
|---|---|---|---|
| ... | High/Med/Low | High/Med/Low | 1-5 |
Top 3 Risks & Mitigations
For each top risk:
- Risk: [Description]
- Early Warning Signs: What would indicate this is happening?
- Prevention: How to reduce likelihood
- Mitigation: How to reduce impact if it occurs
- Owner: Who's responsible for watching this?
Pre-Mortem Insights What did this exercise reveal that wasn't obvious before?
Revised Confidence After this analysis, how confident are you in success? What would increase confidence?
Guidelines
- Be vivid and specific—"the database corrupted" not "something went wrong"
- Include uncomfortable possibilities (key person leaves, competitor moves, we were wrong)
- Don't filter for "that won't happen"—the point is to surface hidden concerns
- Assign real owners to mitigations
- Look for single points of failure
$ARGUMENTS
© neurofoo, 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 premortem of neurofoo/agent-skills.
Open the folder on GitHubat commit 0e7ac2a
Used in 3 other repositories
We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in neurofoo/agent-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Premortem 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 |
|---|---|---|---|---|---|---|
| Premortem this skillneurofoo/agent-skills | 119 | 3 repos | ~568 | Automated safety check: Pass | MIT | |
| Premortemparcadei/Continuous-Claude-v3 | 3.9k | 2 repos | ~3.1k | 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 | |
| Fix Failing Pipelinesa5c-ai/babysitter | 1.8k | — | ~1k | Automated safety check: Pass | MIT | |
| Recipe Post Mortem Setupgoogleworkspace/cli | 31k | — | ~256 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Post Mortem
alirezarezvani/claude-skills
/cs:post-mortem <decision — Honest retrospective on an executed decision, scored against original assumptions and dissent.
Pre Mortem
phuryn/pm-skills
Run a pre-mortem risk analysis on a PRD or launch plan. An agent skill from phuryn/pm-skills.
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.
Premortem
boshu2/agentops
Find how a rollout plan could fail before committing to it. An agent skill from boshu2/agentops.
More from neurofoo/agent-skills
All 22 skills in this repoFive Whys Analysis
neurofoo/agent-skills
Runs a Five Whys root cause analysis, asking why repeatedly from the stated problem until it reaches an actionable cause, then lists corrective actions and verification.
Eisenhower Matrix Prioritizer
neurofoo/agent-skills
Sorts a task list into the four Eisenhower quadrants (do, schedule, delegate, eliminate) with reasons, a time distribution check and first actions.
OODA Loop Analysis
neurofoo/agent-skills
Walks a problem or decision through the OODA loop: observe the facts, orient on causes and assumptions, decide among at least three options, and plan the execution.
Cynefin Problem Classifier
neurofoo/agent-skills
Sorts a problem into the Cynefin domains of simple, complicated, complex, chaotic or confused, then recommends a way of working that fits that domain.
Wardley Map Analysis
neurofoo/agent-skills
Maps a user need's value chain against evolution stages to guide build-versus-buy decisions and show competitive dynamics.
Jtbd
neurofoo/agent-skills
Jobs to Be Done analysis to understand what customers really want.
Questions about Premortem
What does Premortem do?
Pre-mortem analysis that imagines a plan has failed, then works backward to identify causes and preventions. Premortem is an agent skill from neurofoo/agent-skills. Pre-mortem analysis that imagines a plan has failed, then works backward to identify causes and preventions.
How do I install Premortem in Claude Code?
Run `npx skills add neurofoo/agent-skills --skill premortem -a claude-code`. Or copy the skill folder (premortem in neurofoo/agent-skills) into .claude/skills/premortem in your project. Claude Code loads it when a task matches its description.
How do I install Premortem in Codex?
Run `npx skills add neurofoo/agent-skills --skill premortem -a codex`. Or copy the skill folder (premortem in neurofoo/agent-skills) into .agents/skills/premortem in your project. Codex loads it when a task matches its description.
Can I use Premortem 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 neurofoo/agent-skills --skill premortem -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/premortem, .gemini/skills/premortem, .github/skills/premortem and .opencode/skills/premortem in your project.
What does Premortem need to run?
SKILL.md names no scripts, command-line tools or credentials: Premortem is instructions for the agent only.
Does Premortem 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 Premortem 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 Premortem use?
Premortem 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 Premortem use?
About 568 tokens (SKILL.md is roughly 2.3k 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 Premortem?
Skills that share tags, products or a category with Premortem: Premortem (parcadei/Continuous-Claude-v3, 3.9k stars), Post Mortem (alirezarezvani/claude-skills, 28k stars), Pre Mortem (phuryn/pm-skills, 27k stars) and Fix Failing Pipelines (a5c-ai/babysitter, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Premortem?
neurofoo (a GitHub user) maintains it in neurofoo/agent-skills, which has 119 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on January 19, 2026.
Source: neurofoo/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.