/what-if-oracle

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

What-If Oracle — Possibility Space Explorer

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.

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.

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)

When to Use This Skill

Use the Oracle when the user:

• Asks "what if…", "what would happen if…", or "explore the possibilities"
• Faces a fork-in-the-road decision with no obvious answer
• Wants best-case / worst-case / likely-case analysis with probabilities
• Needs contingency planning, risk mapping, or strategic option comparison
• Wants to stress-test an idea or think through second-order consequences

For domain-specific framing (startup, tech architecture, crisis response, etc.), see [references/scenario-templates.md](references/scenario-templates.md).

Core Principle: 0·IF·1

Every scenario analysis has three elements:

• **0** — The unexpressed state (what hasn't happened yet, the potential)
• **1** — The expressed state (what IS, the current reality)
• **IF** — The conditional bond (the decision, event, or change that transforms 0 into 1)

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.

How to Run the Oracle

Phase 1 — Frame the Question

Take the user's What-If question and sharpen it:

**Decompose into components:**

• **The Variable:** What specific thing changes? (one variable per analysis)
• **The Magnitude:** By how much? (quantify if possible)
• **The Timeframe:** Over what period?
• **The Context:** What's the current state before the change?

**If the question is vague, sharpen it:**

• "What if AI takes over?" → "What if 40% of current knowledge-work tasks are automated by AI within 3 years in [specific industry]?"
• "What if we fail?" → "What if monthly revenue stays below $5K for 6 consecutive months starting now?"

Present the sharpened question to the user for confirmation before proceeding.

Phase 2 — Map the Possibility Space

Generate **4-6 scenario branches** using this framework:

| Branch | Definition | Purpose | | ------------------ | ---------------------------------------------------------------------------- | -------------------------------------------------- | | **Ω Best Case** | Everything goes right. Key assumptions all validate. Lucky breaks occur. | Define the ceiling — what's the maximum upside? | | **α Likely Case** | Most probable path given current evidence. No major surprises. | Anchor expectations in reality | | **Δ Worst Case** | Key assumptions fail. Two things go wrong simultaneously. | Define the floor — what's the maximum downside? | | **Ψ Wild Card** | An unexpected variable enters that nobody is tracking. Black swan territory. | Stress-test for the unimaginable | | **Φ Contrarian** | The opposite of the consensus view turns out to be true. | Challenge groupthink and reveal hidden assumptions | | **∞ Second Order** | The first-order effects trigger cascading consequences nobody predicted. | Map the ripple effects |

Phase 3 — Analyze Each Branch

For each scenario branch, provide:

╔══════════════════════════════════════════════╗
║  BRANCH: [Ω/α/Δ/Ψ/Φ/∞] — [Branch Name]    ║
╠══════════════════════════════════════════════╣
║  Probability: [X%]                           ║
║  Timeframe: [When this could materialize]    ║
║  Confidence: [HIGH/MEDIUM/LOW]               ║
╠══════════════════════════════════════════════╣
║  NARRATIVE:                                  ║
║  [2-3 sentences describing how this          ║
║   scenario unfolds step by step]             ║
║                                              ║
║  KEY ASSUMPTIONS:                            ║
║  • [What must be true for this to happen]    ║
║  • [And this]                                ║
║                                              ║
║  TRIGGER CONDITIONS:                         ║
║  • [Early signal that this branch is         ║
║    becoming reality]                         ║
║  • [Second signal]                           ║
║                                              ║
║  CONSEQUENCES:                               ║
║  → Immediate: [What happens first]           ║
║  → 30 days: [What follows]                   ║
║  → 6 months: [Where it leads]               ║
║                                              ║
║  REQUIRED RESPONSE:                          ║
║  [What action to take if this branch         ║
║   activates — specific, actionable]          ║
║