what-if-oracle
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.
What this skill does
# 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] ║
║ ║
║ 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 futRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.