premortem

Solid

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.

AI & Automation 2 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 78/100

Stars 20%
16
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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*...

Details

Author
NewAbra
Repository
NewAbra/auto-co-meta
Created
11 months ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

thinking-pre-mortem

Imagine a project has failed and work backward to identify why. Use at project kickoffs, before major decisions, or when optimism may be obscuring risks.

1 Updated today
babypochi06
Code & Development Listed

premortem

Use before committing to a non-trivial plan, design, architecture, migration, launch, or irreversible decision — especially when momentum or optimism is high and nobody has named what could go wrong. Triggers when you're about to start executing a plan, when stakes are high or the decision is hard to reverse, or when the user asks to stress-test, pressure-test, or sanity-check an approach. Not for generating ideas (that's brainstorming).

0 Updated yesterday
mickzijdel
AI & Automation Solid

premortem

Run a premortem on any plan, launch, product, hire, strategy, or decision. Assumes it already failed 6 months from now and works backward to find every reason why. Produces a revised plan with blind spots exposed. MANDATORY TRIGGERS: 'premortem this', 'premortem my', 'run a premortem', 'what could kill this', 'future-proof this', 'stress test this plan', 'what am i missing here', 'find the blind spots'. STRONG TRIGGERS: 'what could go wrong', 'am i missing anything', 'poke holes in this', 'where will this break', 'devil's advocate this'. Do NOT trigger on simple feedback requests, factual questions, or LLM Council requests. DO trigger when someone has a plan or commitment where the cost of being wrong is high.

2 Updated 3 days ago
0xUrsanomics