inversion-premortem

Identify failure modes and root causes for plans using inversion and pre-mortem reasoning.

7|2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/AndurilCode/craftwork --skill inversion-premortem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inversion-premortem
Source: https://github.com/AndurilCode/craftwork/tree/main/skills/inversion-premortem
Command: npx skills add https://github.com/AndurilCode/craftwork --skill inversion-premortem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps you evaluate whether a plan, strategy, architecture, feature, or decision is likely to fail before execution by identifying hidden failure modes, assumptions, and risks early.

Core Features & Use Cases

  • Inversion (Failure Mode Discovery): Defines how success would fail completely, then enumerates failure conditions and checks whether each is currently guarded against.
  • Pre-mortem (Failure Story Construction): Imagines the project 12 months later after a bad failure, then traces the 3–5 root causes and maps early warning signals back to today.
  • Risk-Driven Mitigations: Produces a concrete risk register with mitigations, early warning metrics, and reversibility assessments for high-likelihood unguarded failures.

Use case example: Before launching a new feature, uncover which assumptions about adoption, third-party dependencies, or team execution would most likely cause it to fail—and define what would signal the risk early.

Quick Start

Apply inversion-premortem to my plan for launching feature X and generate a failure modes table with likelihood, guarded status, hidden assumptions, and targeted mitigations.

Frequently Asked Questions about inversion-premortem

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a pre-mortem analysis to identify failure modes in my project plan?

A pre-mortem analysis imagines your project failing 12 months later, then traces root causes back to today. This process enumerates failure conditions and checks whether your plan is currently guarded against each one, exposing hidden assumptions and blind spots.

What is inversion reasoning for risk assessment and when should I use it?

Inversion reasoning defines how a plan would fail completely, then identifies specific failure conditions to check if they are guarded. Use it to proactively evaluate proposals before commitment or stress-test existing product, technical, and organizational decisions.

How do I uncover hidden assumptions in a feature launch before committing to execution?

To uncover hidden assumptions, apply inversion and pre-mortem reasoning to map adoption, third-party dependency, and team execution risks. This generates a failure modes table with likelihood, guarded status, and early warning signals mapped back to today.

Can I use pre-mortem reasoning to validate technical architecture decisions and organizational strategy?

Yes, pre-mortem reasoning applies to proactive evaluation of proposals before commitment and stress-testing of existing systems. It handles product, technical, and organizational decisions by producing a future-dated failure narrative with root causes.

What's the best way to create a risk register with mitigations and monitoring metrics?

The best way to create a risk register is to generate mitigation actions for high-likelihood unguarded failures, complete with early warning metrics and reversibility assessments. This ensures your risk-driven mitigations are concrete and monitored.

What are the limitations of using pre-mortem analysis for strategy validation?

Pre-mortem analysis relies on accurately imagining future failure scenarios and tracing root causes, meaning its output is only as comprehensive as the identified failure conditions. It complements but does not replace active execution monitoring and post-launch reviews.