agentleFS
qinyan-aiqinyan-ai/qinyan-academic-skills/skills/04-研究方法与科学思维/what-if-oracle/SKILL.md

what-if-oracle

Skill80 starsChanged 8 months agoMITView on GitHub

Run structured What-If scenario analysis with multi-branch possibility exploration. Use this skill when the user asks speculative questions like "what if...", "what would happen if...", "what are the possibilities", "explore scenarios", "scenario analysis", "possibility space", "what could go wrong", "best case / worst case", "risk analysis", "contingency planning", "strategic options", or any question about uncertain futures. Also trigger when the user faces a fork-in-the-road decision, wants to stress-test an idea, or needs to think through consequences before committing.

7 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use database-lookup.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • uppifyagencySkill

    database-lookup

    Search 78 public scientific, biomedical, materials science, and economic databases via REST APIs. Covers physics/astronomy (NASA, NIST, SDSS, SIMBAD), earth/environment (USGS, NOAA, EPA), chemistry/drugs (PubChem, ChEMBL, DrugBank, FDA, KEGG, ZINC, BindingDB), materials (Materials Project, COD), biology/genomics (Reactome, UniProt, STRING, Ensembl, NCBI Gene, GEO, GTEx, PDB, AlphaFold, InterPro, BioGRID, Gene Ontology, dbSNP, gnomAD, ENCODE, Human Protein Atlas, Human Cell Atlas), disease/clinical (COSMIC, Open Targets, ClinicalTrials.gov, OMIM, ClinVar, GDC/TCGA, cBioPortal, DisGeNET, GWAS Catalog), regulatory (FDA, USPTO, SEC EDGAR), economics/finance (FRED, World Bank, US Treasury), demographics (US Census, Eurostat, WHO). Use when looking up compounds, genes, proteins, pathways, variants, clinical trials, patents, economic indicators, or any public database API query.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 8 are common, 0 are distinctive, and 0 are very specific to this project.

  • 8

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Every scenario analysis has three elements:

    line 20
  2. Common:

    After analyzing all branches, provide:

    line 104
  3. Common:

    When evidence exists, weight primary scenarios using the golden ratio:

    line 127
  4. Common:

    All 6 branches. Full analysis with consequences, triggers, and synthesis.

    line 142
  5. Common:

    Start from a desired outcome and work backward: "What conditions must be true for X to happen?

    line 150
  6. Common:

    Not a prediction — it's a possibility map.

    line 158
  7. Common:

    Not a crystal ball — probabilities are estimates based on available evidence, not certainties.

    line 159
  8. Common:

    Not a substitute for action — the best scenario analysis in the world is worthless without subsequent decision and execution.

    line 160

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 Statement 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 Statement (DOI: 10.5281/zenodo.18736841) | IDNA Consolidation v2 (DOI: 10.5281/zenodo.18807387)

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:

BranchDefinitionPurpose
Ω Best CaseEverything goes right. Key assumptions all validate. Lucky breaks occur.Define the ceiling — what's the maximum upside?
α Likely CaseMost probable path given current evidence. No major surprises.Anchor expectations in reality
Δ Worst CaseKey assumptions fail. Two things go wrong simultaneously.Define the floor — what's the maximum downside?
Ψ Wild CardAn unexpected variable enters that nobody is tracking. Black swan territory.Stress-test for the unimaginable
Φ ContrarianThe opposite of the consensus view turns out to be true.Challenge groupthink and reveal hidden assumptions
∞ Second OrderThe 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.

Built By

AHK Strategies — AI Horizon Knowledge Full platform: themindbook.app Research: The What-If Statement (DOI: 10.5281/zenodo.18736841)

"The future is not empty. It contains completed states that exert pull on the present."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.