What is assumption-buster used for?

To break out of boxed thinking by flipping, removing, or exaggerating assumptions and generating new solution angles.

What mode options are available?

You can use --opposite, --zero, or --10x to transform each assumption.

What happens after identifying top picks?

Move the top 2–3 ideas to a planning step (/ctx:plan or Tasks) for execution.

assumption-buster

Scanned

npx machina-cli add skill NickCrew/claude-cortex/assumption_buster --openclaw

Files (1)

SKILL.md

999 B

`/collaboration:assumption-buster`

Use when the team feels boxed in or every idea sounds the same.

Inputs

Topic or problem statement
Known assumptions/constraints (even if informal)
Optional mode flag: --opposite, --zero, or --10x

Steps

List core assumptions (facts, beliefs, constraints).
Transform each via chosen operator (opposite/zero/10x).
Generate 1–2 reframed ideas per transformed assumption.
Capture evidence to collect and a fast test for each idea.
Pick the most promising 2–3 and move to /ctx:plan or Tasks.

Output Template

### Assumptions
### Transforms (opposite/zero/10x)
### Reframed Ideas
- Idea … (evidence, fast test)
### Top Picks

Pairings

Run before /collaboration:idea-lab if you need to loosen constraints.
Feed winners into /collaboration:concept-forge to score/prioritize.

Source

git clone https://github.com/NickCrew/claude-cortex/blob/main/skills/collaboration/assumption_buster/SKILL.mdView on GitHub

Overview

Assumption-buster helps teams break out of boxed thinking by flipping, removing, or exaggerating core assumptions. It uses structured transforms (--opposite, --zero, or --10x) to generate fresh angles and quick tests when ideas feel repetitive.

How This Skill Works

Provide a topic or problem, list known assumptions, and optionally set a mode (--opposite, --zero, or --10x). Transform each assumption with the chosen operator to create 1–2 reframed ideas per transformed assumption, then capture evidence and a fast test for each idea, finally selecting the top 2–3 to move into planning.

When to Use It

When the team feels boxed in or every idea sounds the same.
When you want fresh angles by flipping or exaggerating constraints.
During brainstorming to loosen rigid constraints before collaborating sessions.
When you need rapid reframing to test viability of alternate approaches.
Before moving ideas to planning to ensure multiple viable options exist.

Quick Start

Step 1: Provide Topic/Problem and list known assumptions.
Step 2: Choose a mode (--opposite, --zero, or --10x) if desired.
Step 3: Transform each assumption, generate 1–2 reframed ideas, collect evidence and a fast test, then pick top 2–3 for planning.

Best Practices

List all core assumptions explicitly before transforming.
Apply one operator per assumption to keep results clear and interpretable.
Aim for 1–2 reframed ideas per transformed assumption.
Document evidence and a fast test for each idea.
Select the top 2–3 ideas to advance to planning (/ctx:plan or Tasks).

Example Use Cases

Product team flips customer constraints to explore broader feature ideas.
Marketing reframes value by exaggerating benefits (10x) to stress-test messaging.
Operations removes a baseline constraint to identify process simplifications.
Strategy session uses opposite thinking to challenge prevailing industry assumptions.
Education platform tests 1–2 extreme scenarios to validate resilience of learning paths.

Frequently Asked Questions

Add this skill to your agents