🛠️ What If Oracle
不確実な未来や意思決定の岐路に際し、多岐にわたる可能性を構造的に分析し、もしものシナリオを深く探求するSkill。
📺 まず動画で見る(YouTube)
▶ 【衝撃】最強のAIエージェント「Claude Code」の最新機能・使い方・プログラミングをAIで効率化する超実践術を解説! ↗
※ jpskill.com 編集部が参考用に選んだ動画です。動画の内容と Skill の挙動は厳密には一致しないことがあります。
📜 元の英語説明(参考)
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.
🇯🇵 日本人クリエイター向け解説
不確実な未来や意思決定の岐路に際し、多岐にわたる可能性を構造的に分析し、もしものシナリオを深く探求するSkill。
※ jpskill.com 編集部が日本のビジネス現場向けに補足した解説です。Skill本体の挙動とは独立した参考情報です。
⚠️ ダウンロード・利用は自己責任でお願いします。当サイトは内容・動作・安全性について責任を負いません。
🎯 このSkillでできること
下記の説明文を読むと、このSkillがあなたに何をしてくれるかが分かります。Claudeにこの分野の依頼をすると、自動で発動します。
📦 インストール方法 (3ステップ)
- 1. 上の「ダウンロード」ボタンを押して .skill ファイルを取得
- 2. ファイル名の拡張子を .skill から .zip に変えて展開(macは自動展開可)
- 3. 展開してできたフォルダを、ホームフォルダの
.claude/skills/に置く- · macOS / Linux:
~/.claude/skills/ - · Windows:
%USERPROFILE%\.claude\skills\
- · macOS / Linux:
Claude Code を再起動すれば完了。「このSkillを使って…」と話しかけなくても、関連する依頼で自動的に呼び出されます。
詳しい使い方ガイドを見る →- 最終更新
- 2026-05-17
- 取得日時
- 2026-05-17
- 同梱ファイル
- 2
💬 こう話しかけるだけ — サンプルプロンプト
- › What If Oracle を使って、最小構成のサンプルコードを示して
- › What If Oracle の主な使い方と注意点を教えて
- › What If Oracle を既存プロジェクトに組み込む方法を教えて
これをClaude Code に貼るだけで、このSkillが自動発動します。
📖 Claude が読む原文 SKILL.md(中身を展開)
この本文は AI(Claude)が読むための原文(英語または中国語)です。日本語訳は順次追加中。
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:
| 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.
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."
同梱ファイル
※ ZIPに含まれるファイル一覧。`SKILL.md` 本体に加え、参考資料・サンプル・スクリプトが入っている場合があります。
- 📄 SKILL.md (9,481 bytes)
- 📎 references/scenario-templates.md (4,150 bytes)