Skip to content
Skills Library
Management & product · Analysis

inversion

/inversion

Use inversion to solve problems by reasoning backward from failure, bad outcomes, or the opposite of success. Use when identifying risks, running premortems, or escaping overly idealized thinking.

Licence
MIT
Last repository change
09.05.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 09.05.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use inversion to solve problems by reasoning backward from failure, bad outcomes, or the opposite of success. Use when identifying risks, running premortems, or escaping overly idealized thinking.

Original author description

Use inversion to solve problems by reasoning backward from failure, bad outcomes, or the opposite of success. Use when identifying risks, running premortems, or escaping overly idealized thinking.

How it works

  1. Overview
  2. How to Use Inversion
  3. Practical Example: Pre-Mortem
  4. Key Benefit
  5. Sources
Original SKILL.md headings · 45 lines, 181 words
SKILL.md preview
---
name: inversion
description: Use inversion to solve problems by reasoning backward from failure, bad outcomes, or the opposite of success. Use when identifying risks, running premortems, or escaping overly idealized thinking.
license: MIT
metadata:
  author: itzcull
---

# Inversion

## Overview
- **Category**: Problem Solving
- **Purpose**: Approach a problem from a different perspective

## How to Use Inversion

### Trigger Questions
- "Am I only thinking of ideal solutions or scenarios?"

### Steps
1. Ask: "What would be the worst decision/solution in this situation?"
2. Identify why it would be bad
3. Develop a good solution by examining reasons for bad decisions

### Guiding Questions
- How could this go wrong?
- What would the opposite of this be?
- What would make a bad solution to this?

## Practical Example: Pre-Mortem

Project managers use inversion through a "pre-mortem" exercise:
- Imagine the project has failed six months from now
- Examine potential failure scenarios
- Ask questions like:
  - "What went wrong?"
  - "What mistakes did we make?"
  - "Why did this project fail?"

## Key Benefit
Inversion helps you:
- See potential bad outcomes
- Anticipate and avoid potential mistakes
- Gain a different perspective on problems

## Sources
- "Mental models for designers" by Wes O'Haire
- "Inversion" by James Clear

---
**Source**: [https://untools.co/inversion/](https://untools.co/inversion/)

Versions

RepositoryScoreLicence
This page · itzcull/thinking-skills100MIT
aleknitka/agent-creative-thinking-skills100MIT
danium/lateral-thinking100MIT
deciqAI/knowledge-skills100MIT
guia-matthieu/clawfu-skills95MIT
jacob-balslev/skill-graph90Apache-2.0
saadshahd/moo.md82MIT

Database snapshot: 13.11.2026 · package version 7b527e043f9f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100inversion-thinking-pre-mortems-failure-modes
    Use this skill when conducting project pre-mortems, inverting technical plans, and identifying catastrophic failure modes in advance.
  • 100mental-models
    Apply mental models — your own, or 21 sourced ones — to any problem. Use when user requests decision analysis, says "help me think", "apply mental model", mentions model names (inversion, bottlenecks, second-order thinking), or needs structured thinking frameworks.
  • 85insight-premortem
    Find plausible failure paths before committing to a plan. Use for a premortem or "how could this plan fail?" For an observed failure use insight-root-cause; for broad critique use insight-adversarial.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.