
What-If Oracle
FreeExplore uncertain futures with structured scenario analysis.
Free · Opens the source repo
What What-If Oracle does
The What-If Oracle skill provides a systematic approach to exploring uncertain futures through structured scenario analysis. It operates on the principle that asking speculative questions is a fundamental cognitive operation, allowing users to simulate various outcomes before making decisions. By mapping out a full possibility space, the Oracle helps users visualize multiple branching timelines, each with its own logic, probability, and consequences. This is particularly useful for strategic planning, risk assessment, and decision-making in complex environments.
To effectively use the What-If Oracle, users start by framing their questions to clarify the specific variables, magnitudes, timeframes, and contexts involved. This precision is crucial; vague questions yield vague analyses. Once the question is sharpened, the Oracle generates 4-6 scenario branches, including best-case, likely-case, worst-case, and others, each providing a different perspective on potential outcomes. This multi-branch approach allows users to consider a range of possibilities, from the most optimistic to the most pessimistic, and even unexpected events that could arise.
After mapping the scenarios, users analyze each branch to understand the probabilities, timelines, and key assumptions that underpin each outcome. This analysis includes a narrative of how each scenario might unfold, as well as the immediate and longer-term consequences. Finally, users synthesize the findings to create a probability distribution, which visually represents the likelihood of each scenario occurring. This comprehensive analysis equips users with actionable insights, enabling them to make informed decisions based on a thorough understanding of potential futures.
The What-If Oracle is ideal for professionals involved in strategic planning, project management, and risk analysis who need to navigate uncertainty and make decisions based on a variety of possible outcomes. By employing this skill, users can stress-test their ideas and prepare for various contingencies, ensuring they are better equipped to handle the complexities of their respective fields.
When to use it
Use this skill when faced with speculative questions about future scenarios, strategic forks, or when needing to assess risks and opportunities.
When not to use it
This skill may not be suitable for straightforward decisions with clear outcomes or when immediate action is required without extensive analysis.
What you can build with it
Strategic Planning Session
In a team meeting, a manager uses the Oracle to explore potential outcomes of entering a new market, analyzing best, likely, and worst-case scenarios.
Risk Assessment for New Product Launch
A product manager employs the skill to evaluate the risks associated with a new product launch, mapping out possible market reactions and competitor actions.
Crisis Response Strategy
During a crisis, a leader uses the Oracle to assess various response strategies, considering the implications of each action on stakeholders and resources.
How to install What-If Oracle
View source1. Install with the skills CLI
npx skills add k-dense-ai/scientific-agent-skills/what-if-oracle --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by k-dense-aiWhat-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) | IDNA v2 / Unified Digital Consciousness Theory (DOI: 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.
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] ║
║ ║
║ WHAT MOST PEOPLE MISS: ║
║ [The non-obvious insight about this ║
║ scenario that conventional analysis ║
║ would overlook] ║
╚══════════════════════════════════════════════╝
Phase 4 — Synthesis
After analyzing all branches, provide:
Probability Distribution:
Ω Best Case ····· [██████░░░░] 15%
α Likely Case ··· [████████░░] 45%
Δ Worst Case ···· [██████░░░░] 20%
Ψ Wild Card ····· [███░░░░░░░] 8%
Φ Contrarian ···· [████░░░░░░] 7%
∞ Second Order ·· [███░░░░░░░] 5%
Robust Actions: What actions are beneficial across MULTIPLE branches? These are the no-regret moves — do them regardless of which future materializes.
Hedge Actions: What preparations protect against the worst branches without sacrificing upside?
Decision Triggers: What specific, observable signals should cause you to update which branch is most likely? Define the tripwires.
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.
Golden Ratio Weighting
When evidence exists, weight primary scenarios using the golden ratio:
- Primary future (most likely): 61.8% of attention/resources
- Alternative future: 38.2% of attention/resources
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.
Modes
Quick Oracle (2-3 minutes)
3 branches only: Best, Likely, Worst. Short narratives. For fast decisions.
Deep Oracle (5-10 minutes)
All 6 branches. Full analysis with consequences, triggers, and synthesis. For high-stakes decisions.
Scenario Chain
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.
Reverse Oracle
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.
Competitive Oracle
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?"
What This Is NOT
- Not a prediction — it's a possibility map. The Oracle doesn't claim to know the future; it helps you prepare for multiple futures.
- Not a crystal ball — probabilities are estimates based on available evidence, not certainties.
- Not a substitute for action — the best scenario analysis in the world is worthless without subsequent decision and execution.
Reference Files
| File | Purpose |
|---|---|
| references/scenario-templates.md | Domain-specific templates (startup, tech, finance, crisis, etc.) and probability calibration |
License
© 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.
Frequently asked questions about What-If Oracle
Similar skills
Competitive Analysis
Build detailed competitive landscape decks efficiently.
Brand Discovery
Structured interviews to articulate brand identity.
CrossFrame Org
Facilitates structured organizational analysis and repair.
Technical Product Pricing
Optimize your pricing strategy for technical products.
Product-Led Growth
Optimize your go-to-market strategy with data-driven insights.
Positioning Strategy
Own your market position with clear differentiation.
