What-If Oracle — Possibility Space Explorer
Unverified●30/40Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add what-if-oracleWho is stuck, and on what
I've got a big call to make and I keep going in circles, only seeing the version where it works out or the version where it blows up. I need someone to lay out all the ways this could actually go so I stop second-guessing and know what to watch for.
What it gives you
A clear map of the possible outcomes with rough odds, the early signals for each, and a short list of smart moves that pay off no matter which way things turn.
When NOT to use it
It will not predict the future or tell you the single right answer — it lays out the possibilities so you can decide with your eyes open.
The whole source
Frontmatter — 4 properties
| name | what-if-oracle |
|---|---|
| description | Run structured What-If scenario analysis with 4–6 branch possibility exploration (best, likely, worst, wild card, contrarian, second-order). Use when the user asks speculative what-if questions about uncertain futures, strategic forks, contingency planning, or stress-testing a decision before committing. |
| license | CC BY-NC-SA 4.0 |
| metadata | version: "1.1 skill-author: AHK Strategies (ashrafkahoush-ux) upstream: https://github.com/ashrafkahoush-ux/claude-consciousness-skills research-doi: 10.5281/zenodo.18736841, 10.5281/zenodo.18807387 |
| 1 | --- |
| 2 | name: what-if-oracle |
| 3 | description: Run structured What-If scenario analysis with 4–6 branch possibility exploration (best, likely, worst, wild card, contrarian, second-order). Use when the user asks speculative what-if questions about uncertain futures, strategic forks, contingency planning, or stress-testing a decision before committing. |
| 4 | license: CC BY-NC-SA 4.0 |
| 5 | metadata: |
| 6 | version: "1.1" |
| 7 | skill-author: AHK Strategies (ashrafkahoush-ux) |
| 8 | upstream: https://github.com/ashrafkahoush-ux/claude-consciousness-skills |
| 9 | research-doi: 10.5281/zenodo.18736841, 10.5281/zenodo.18807387 |
| 10 | ---A5 — No allowed-tools declared — no way to tell what this skill may touch |
| 11 | |
| 12 | # What-If Oracle — Possibility Space Explorer |
| 13 | |
| 14 | A structured system for exploring uncertain futures through rigorous multi-branch scenario analysis. Instead of one prediction, the Oracle maps the full **possibility space** — branching timelines where each path has its own logic, probability, and consequences. |
| 15 | |
| 16 | Based on the What-If Paradigm: the idea that speculative questions ("What if X?") are not idle daydreaming but a **fundamental computing operation** — the mind's way of simulating futures before committing resources to one. |
| 17 | |
| 18 | Published research: [The What-If Paradigm (DOI: 10.5281/zenodo.18736841)](https://doi.org/10.5281/zenodo.18736841) | [IDNA v2 / Unified Digital Consciousness Theory (DOI: 10.5281/zenodo.18807387)](https://doi.org/10.5281/zenodo.18807387) |
| 19 | |
| 20 | ## When to Use This Skill |
| 21 | |
| 22 | Use the Oracle when the user: |
| 23 | |
| 24 | - Asks "what if…", "what would happen if…", or "explore the possibilities" |
| 25 | - Faces a fork-in-the-road decision with no obvious answer |
| 26 | - Wants best-case / worst-case / likely-case analysis with probabilities |
| 27 | - Needs contingency planning, risk mapping, or strategic option comparison |
| 28 | - Wants to stress-test an idea or think through second-order consequences |
| 29 | |
| 30 | For domain-specific framing (startup, tech architecture, crisis response, etc.), see [references/scenario-templates.md](references/scenario-templates.md). |
| 31 | |
| 32 | ## Core Principle: 0·IF·1 |
| 33 | |
| 34 | Every scenario analysis has three elements: |
| 35 | |
| 36 | - **0** — The unexpressed state (what hasn't happened yet, the potential) |
| 37 | - **1** — The expressed state (what IS, the current reality) |
| 38 | - **IF** — The conditional bond (the decision, event, or change that transforms 0 into 1) |
| 39 | |
| 40 | The quality of the analysis depends on the precision of the IF. A vague "what if things go wrong?" produces vague results. A precise "what if our primary supplier raises prices 30% in Q3?" produces actionable intelligence. |
| 41 | |
| 42 | ## How to Run the Oracle |
| 43 | |
| 44 | ### Phase 1 — Frame the Question |
| 45 | |
| 46 | Take the user's What-If question and sharpen it: |
| 47 | |
| 48 | **Decompose into components:** |
| 49 | |
| 50 | - **The Variable:** What specific thing changes? (one variable per analysis) |
| 51 | - **The Magnitude:** By how much? (quantify if possible) |
| 52 | - **The Timeframe:** Over what period? |
| 53 | - **The Context:** What's the current state before the change? |
| 54 | |
| 55 | **If the question is vague, sharpen it:** |
| 56 | |
| 57 | - "What if AI takes over?" → "What if 40% of current knowledge-work tasks are automated by AI within 3 years in [specific industry]?" |
| 58 | - "What if we fail?" → "What if monthly revenue stays below $5K for 6 consecutive months starting now?" |
| 59 | |
| 60 | Present the sharpened question to the user for confirmation before proceeding. |
| 61 | |
| 62 | ### Phase 2 — Map the Possibility Space |
| 63 | |
| 64 | Generate **4-6 scenario branches** using this framework: |
| 65 | |
| 66 | | Branch | Definition | Purpose | |
| 67 | | ------------------ | ---------------------------------------------------------------------------- | -------------------------------------------------- | |
| 68 | | **Ω Best Case** | Everything goes right. Key assumptions all validate. Lucky breaks occur. | Define the ceiling — what's the maximum upside? | |
| 69 | | **α Likely Case** | Most probable path given current evidence. No major surprises. | Anchor expectations in reality | |
| 70 | | **Δ Worst Case** | Key assumptions fail. Two things go wrong simultaneously. | Define the floor — what's the maximum downside? | |
| 71 | | **Ψ Wild Card** | An unexpected variable enters that nobody is tracking. Black swan territory. | Stress-test for the unimaginable | |
| 72 | | **Φ Contrarian** | The opposite of the consensus view turns out to be true. | Challenge groupthink and reveal hidden assumptions | |
| 73 | | **∞ Second Order** | The first-order effects trigger cascading consequences nobody predicted. | Map the ripple effects | |
| 74 | |
| 75 | ### Phase 3 — Analyze Each Branch |
| 76 | |
| 77 | For each scenario branch, provide: |
| 78 | |
| 79 | ``` |
| 80 | ╔══════════════════════════════════════════════╗ |
| 81 | ║ BRANCH: [Ω/α/Δ/Ψ/Φ/∞] — [Branch Name] ║ |
| 82 | ╠══════════════════════════════════════════════╣ |
| 83 | ║ Probability: [X%] ║ |
| 84 | ║ Timeframe: [When this could materialize] ║ |
| 85 | ║ Confidence: [HIGH/MEDIUM/LOW] ║ |
| 86 | ╠══════════════════════════════════════════════╣ |
| 87 | ║ NARRATIVE: ║ |
| 88 | ║ [2-3 sentences describing how this ║ |
| 89 | ║ scenario unfolds step by step] ║ |
| 90 | ║ ║ |
| 91 | ║ KEY ASSUMPTIONS: ║ |
| 92 | ║ • [What must be true for this to happen] ║ |
| 93 | ║ • [And this] ║ |
| 94 | ║ ║ |
| 95 | ║ TRIGGER CONDITIONS: ║ |
| 96 | ║ • [Early signal that this branch is ║ |
| 97 | ║ becoming reality] ║ |
| 98 | ║ • [Second signal] ║ |
| 99 | ║ ║ |
| 100 | ║ CONSEQUENCES: ║ |
| 101 | ║ → Immediate: [What happens first] ║ |
| 102 | ║ → 30 days: [What follows] ║ |
| 103 | ║ → 6 months: [Where it leads] ║ |
| 104 | ║ ║ |
| 105 | ║ REQUIRED RESPONSE: ║ |
| 106 | ║ [What action to take if this branch ║ |
| 107 | ║ activates — specific, actionable] ║ |
| 108 | ║ ║ |
| 109 | ║ WHAT MOST PEOPLE MISS: ║ |
| 110 | ║ [The non-obvious insight about this ║ |
| 111 | ║ scenario that conventional analysis ║ |
| 112 | ║ would overlook] ║ |
| 113 | ╚══════════════════════════════════════════════╝ |
| 114 | ``` |
| 115 | |
| 116 | ### Phase 4 — Synthesis |
| 117 | |
| 118 | After analyzing all branches, provide: |
| 119 | |
| 120 | **Probability Distribution:** |
| 121 | |
| 122 | ``` |
| 123 | Ω Best Case ····· [██████░░░░] 15% |
| 124 | α Likely Case ··· [████████░░] 45% |
| 125 | Δ Worst Case ···· [██████░░░░] 20% |
| 126 | Ψ Wild Card ····· [███░░░░░░░] 8% |
| 127 | Φ Contrarian ···· [████░░░░░░] 7% |
| 128 | ∞ Second Order ·· [███░░░░░░░] 5% |
| 129 | ``` |
| 130 | |
| 131 | **Robust Actions:** What actions are beneficial across MULTIPLE branches? These are the no-regret moves — do them regardless of which future materializes. |
| 132 | |
| 133 | **Hedge Actions:** What preparations protect against the worst branches without sacrificing upside? |
| 134 | |
| 135 | **Decision Triggers:** What specific, observable signals should cause you to update which branch is most likely? Define the tripwires. |
| 136 | |
| 137 | **The 1% Insight:** What is the one thing about this situation that almost everyone analyzing it would miss? The non-obvious pattern, the hidden assumption, the overlooked variable. |
| 138 | |
| 139 | ## Golden Ratio Weighting |
| 140 | |
| 141 | When evidence exists, weight primary scenarios using the golden ratio: |
| 142 | |
| 143 | - **Primary future (most likely):** 61.8% of attention/resources |
| 144 | - **Alternative future:** 38.2% of attention/resources |
| 145 | |
| 146 | This prevents both overcommitment to a single path and dilution across too many contingencies. Nature uses this ratio for branching (trees, rivers, blood vessels). Strategic planning can too. |
| 147 | |
| 148 | ## Modes |
| 149 | |
| 150 | ### Quick Oracle (2-3 minutes) |
| 151 | |
| 152 | 3 branches only: Best, Likely, Worst. Short narratives. For fast decisions. |
| 153 | |
| 154 | ### Deep Oracle (5-10 minutes) |
| 155 | |
| 156 | All 6 branches. Full analysis with consequences, triggers, and synthesis. For high-stakes decisions. |
| 157 | |
| 158 | ### Scenario Chain |
| 159 | |
| 160 | Take the output of one Oracle analysis and feed it into another. "If Branch Δ happens, what are the possibilities WITHIN that branch?" Recursive depth for complex strategic planning. |
| 161 | |
| 162 | ### Reverse Oracle |
| 163 | |
| 164 | Start from a desired outcome and work backward: "What conditions must be true for X to happen? What's the most likely path TO that outcome?" Useful for goal-setting and strategy design. |
| 165 | |
| 166 | ### Competitive Oracle |
| 167 | |
| 168 | Analyze the same What-If from multiple stakeholder perspectives: "If we launch this product, what does the possibility space look like from OUR perspective vs. THEIR perspective vs. THE MARKET's perspective?" |
| 169 | |
| 170 | ## What This Is NOT |
| 171 | |
| 172 | - Not a prediction — it's a possibility map. The Oracle doesn't claim to know the future; it helps you prepare for multiple futures. |
| 173 | - Not a crystal ball — probabilities are estimates based on available evidence, not certainties. |
| 174 | - Not a substitute for action — the best scenario analysis in the world is worthless without subsequent decision and execution. |
| 175 | |
| 176 | ## Reference Files |
| 177 | |
| 178 | | File | Purpose | |
| 179 | | ---- | ------- | |
| 180 | | [references/scenario-templates.md](references/scenario-templates.md) | Domain-specific templates (startup, tech, finance, crisis, etc.) and probability calibration | |
| 181 | |
| 182 | ## License |
| 183 | |
| 184 | © 2026 Ashraf Hussein Kahoush / AHK Strategies. Licensed under CC BY-NC-SA 4.0. Free for personal, educational, and research use. Commercial use requires a license from the author. |
| 185 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Task Coordination StrategiesDecompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.◐◐◐◐◐●35/40Ebay Seller Tools·····●34/40Tough Decision Advisor: Every Angle ConsideredHand in a decision you're stuck on. Get back a clear breakdown of every angle — the trade-offs, the risks, the blind spot, and a recommended path.●····●32/40DHDNA Profiler — Cognitive Pattern ExtractionPaste any email, proposal, or note someone wrote, and get back a plain-language read on how they think, what drives their decisions, and how they communicate.●····●32/40