inversion-exercise

Invert core assumptions to reveal hidden constraints and alternative solutions.

2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/ucirello/sgai --skill inversion-exercise-ucirello
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inversion-exercise
Source: https://github.com/ucirello/sgai/tree/main/cmd/sgai/skel/.sgai/skills/problem-solving/inversion-exercise
Command: npx skills add https://github.com/ucirello/sgai --skill inversion-exercise-ucirello

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps overcome mental blocks and rigid thinking by systematically challenging core assumptions, revealing hidden constraints and alternative approaches to problem-solving.

Core Features & Use Cases

  • Assumption Inversion: Flips conventional assumptions to explore "what if the opposite were true?".
  • Constraint Discovery: Uncovers hidden limitations or unexamined necessities in a problem.
  • Alternative Solutions: Generates novel perspectives and potential solutions by questioning the status quo.
  • Use Case: When a development team is stuck on a performance issue and keeps optimizing the same code, this Skill can help them question the fundamental approach, perhaps leading to a redesign that avoids the bottleneck entirely.

Quick Start

Use the inversion-exercise skill to challenge the assumptions behind the slow app performance problem.

Frequently Asked Questions about inversion-exercise

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

FAQPage Schema
What is assumption inversion for problem solving?

Assumption inversion is a problem-solving technique that flips conventional assumptions to explore opposite conditions, revealing hidden constraints and generating alternative approaches. It systematically questions must-be statements to overcome mental blocks and rigid thinking.

How do I challenge assumptions when stuck on a performance issue?

To challenge assumptions during a performance issue, systematically question the fundamental approach and must-be statements. Instead of optimizing existing code, explore what if the opposite conditions were true to reveal hidden constraints and prompt a complete redesign.

When do I need to use assumption inversion?

You need assumption inversion when conventional solutions are insufficient or a fresh perspective is needed. It is applicable in scenarios where a development team is stuck on a problem and keeps applying the same ineffective optimization approaches.

What's the best way to find hidden constraints in a problem?

The best way to find hidden constraints is by systematically questioning core assumptions and exploring the implications of opposite conditions. This constraint discovery process uncovers hidden limitations and unexamined necessities by questioning the status quo.

Are there limitations to using assumption inversion for creativity?

A limitation of assumption inversion for creativity is that it requires systematically questioning fundamental must-be statements, which may not suit rigid environments. It focuses on revealing alternative approaches rather than providing direct technical implementations.