Back to skills
SkillHub ClubShip Full StackFull Stack

premortem

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.

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars
50
Hot score
91
Updated
March 20, 2026
Overall rating
C2.3
Composite score
2.3
Best-practice grade
B77.6

Install command

npx @skill-hub/cli install neurofoo-agent-skills-premortem

Repository

neurofoo/agent-skills

Skill path: premortem

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.

Open repository

Best for

Primary workflow: Ship Full Stack.

Technical facets: Full Stack.

Target audience: everyone.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: neurofoo.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

  • Install premortem into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
  • Review https://github.com/neurofoo/agent-skills before adding premortem to shared team environments
  • Use premortem for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
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
premortem | SkillHub