mirror of
https://github.com/K-Dense-AI/claude-scientific-skills.git
synced 2026-03-27 07:09:27 +08:00
feat: add cognitive science skills — consciousness-council, dhdna-profiler, what-if-oracle
Three research-backed cognitive science skills: - consciousness-council: 12-archetype Mind Council deliberation for structured multi-perspective analysis - dhdna-profiler: cognitive fingerprinting across 12 dimensions (DOI: 10.5281/zenodo.18736629) - what-if-oracle: multi-branch scenario analysis with probability weighting (DOI: 10.5281/zenodo.18736841) Each includes reference documentation. All MIT licensed. Source: https://github.com/ashrafkahoush-ux/Claude-consciousness-skills
This commit is contained in:
168
scientific-skills/what-if-oracle/SKILL.md
Normal file
168
scientific-skills/what-if-oracle/SKILL.md
Normal file
@@ -0,0 +1,168 @@
|
||||
---
|
||||
name: what-if-oracle
|
||||
description: 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.
|
||||
allowed-tools: Read Write
|
||||
license: MIT license
|
||||
metadata:
|
||||
skill-author: AHK Strategies (ashrafkahoush-ux)
|
||||
---
|
||||
|
||||
# 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)](https://doi.org/10.5281/zenodo.18736841) | [IDNA Consolidation v2 (DOI: 10.5281/zenodo.18807387)](https://doi.org/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](https://ahkstrategies.net) — AI Horizon Knowledge
|
||||
Full platform: [themindbook.app](https://themindbook.app)
|
||||
Research: [The What-If Statement (DOI: 10.5281/zenodo.18736841)](https://doi.org/10.5281/zenodo.18736841)
|
||||
|
||||
_"The future is not empty. It contains completed states that exert pull on the present."_
|
||||
@@ -0,0 +1,137 @@
|
||||
# What-If Oracle — Scenario Templates
|
||||
|
||||
Reference guide for domain-specific scenario analysis configurations.
|
||||
|
||||
## Startup / Business Decision
|
||||
|
||||
**Variables to test:**
|
||||
|
||||
- Market entry timing
|
||||
- Pricing strategy
|
||||
- Partnership terms
|
||||
- Hiring decisions
|
||||
- Funding rounds
|
||||
|
||||
**Branch emphasis:** Likely Case + Contrarian + Second Order
|
||||
**Key tension:** Speed vs. thoroughness — startups can't afford to analyze forever
|
||||
|
||||
**Template prompt:**
|
||||
|
||||
> "What if we [specific action] in [timeframe]? Our current state: [revenue, team size, runway]. Key constraint: [the limiting factor]."
|
||||
|
||||
## Technology Architecture
|
||||
|
||||
**Variables to test:**
|
||||
|
||||
- Tech stack choice
|
||||
- Build vs. buy
|
||||
- Scaling approach
|
||||
- Security model
|
||||
- Migration path
|
||||
|
||||
**Branch emphasis:** Worst Case + Wild Card + Second Order
|
||||
**Key tension:** Engineering elegance vs. shipping speed
|
||||
|
||||
**Template prompt:**
|
||||
|
||||
> "What if we choose [technology/approach] for [system]? Current architecture: [brief description]. Team capability: [relevant skills]. Timeline: [deadline]."
|
||||
|
||||
## Investment / Financial
|
||||
|
||||
**Variables to test:**
|
||||
|
||||
- Market conditions
|
||||
- Valuation scenarios
|
||||
- Exit timing
|
||||
- Capital allocation
|
||||
- Revenue model changes
|
||||
|
||||
**Branch emphasis:** All 6 branches — money decisions deserve full analysis
|
||||
**Key tension:** Risk tolerance vs. opportunity cost
|
||||
|
||||
**Template prompt:**
|
||||
|
||||
> "What if [market condition / financial event] happens? Our exposure: [amount/percentage]. Current position: [financial state]. Time horizon: [investment period]."
|
||||
|
||||
## Career / Personal
|
||||
|
||||
**Variables to test:**
|
||||
|
||||
- Job change
|
||||
- Skill development path
|
||||
- Relocation
|
||||
- Relationship decisions
|
||||
- Health changes
|
||||
|
||||
**Branch emphasis:** Likely Case + Best Case + Contrarian
|
||||
**Key tension:** Security vs. growth — comfort zone vs. expansion
|
||||
|
||||
**Template prompt:**
|
||||
|
||||
> "What if I [personal decision]? My current situation: [brief]. What I value most: [1-3 values]. What I'm afraid of: [honest answer]."
|
||||
|
||||
## Geopolitical / Macro
|
||||
|
||||
**Variables to test:**
|
||||
|
||||
- Policy changes
|
||||
- Regulatory shifts
|
||||
- Market disruptions
|
||||
- Technology breakthroughs
|
||||
- Social movements
|
||||
|
||||
**Branch emphasis:** Wild Card + Second Order + Contrarian
|
||||
**Key tension:** Local impact vs. systemic effects
|
||||
|
||||
**Template prompt:**
|
||||
|
||||
> "What if [geopolitical event] happens? My exposure: [how it affects me/my organization]. Time horizon: [relevant period]."
|
||||
|
||||
## Crisis Response
|
||||
|
||||
**Variables to test:**
|
||||
|
||||
- Severity escalation
|
||||
- Communication strategy
|
||||
- Resource allocation
|
||||
- Recovery timeline
|
||||
- Reputation impact
|
||||
|
||||
**Branch emphasis:** Worst Case (detailed) + Likely Case + Second Order
|
||||
**Key tension:** Immediate triage vs. root cause resolution
|
||||
|
||||
**Template prompt:**
|
||||
|
||||
> "We're facing [crisis/incident]. Current impact: [what's broken]. Stakeholders affected: [who]. Resources available: [what we can deploy]. What if [specific escalation scenario]?"
|
||||
|
||||
## The Recursive Template
|
||||
|
||||
For complex, multi-layered analysis:
|
||||
|
||||
```
|
||||
ROUND 1: "What if X?"
|
||||
→ Identify the most likely branch (α)
|
||||
|
||||
ROUND 2: "Given α is happening, what if Y?"
|
||||
→ Identify the most likely sub-branch
|
||||
|
||||
ROUND 3: "Given α+Y, what if Z?"
|
||||
→ Map the deepest consequences
|
||||
|
||||
Each round narrows the possibility space while deepening understanding.
|
||||
Maximum recommended depth: 3 rounds.
|
||||
```
|
||||
|
||||
## Probability Calibration Guide
|
||||
|
||||
When assigning probabilities to branches:
|
||||
|
||||
| Confidence Level | Probability Range | Evidence Required |
|
||||
| ---------------- | ----------------- | ---------------------------------------------------------- |
|
||||
| **Very High** | >80% | Strong historical precedent + current data alignment |
|
||||
| **High** | 60-80% | Multiple converging signals, some historical support |
|
||||
| **Medium** | 30-60% | Mixed signals, could go either way |
|
||||
| **Low** | 10-30% | Plausible but requires several things to go a specific way |
|
||||
| **Very Low** | <10% | Black swan territory — possible but unlikely |
|
||||
|
||||
**Rule:** All branch probabilities in a single analysis should sum to approximately 100%. If they don't, there's a missing branch.
|
||||
Reference in New Issue
Block a user