
What If Oracle
Run structured what-if scenario analysis before major business, architecture, investment, or career decisions without ad-hoc guesswork.
Overview
What-If Oracle is a journey-wide agent skill that supplies domain-specific scenario templates and branch emphasis—usable whenever a solo builder needs to stress-test a major decision before committing.
Install
npx skills add https://github.com/k-dense-ai/scientific-agent-skills --skill what-if-oracleWhat is this skill?
- Four domain packs: startup/business, technology architecture, investment/financial, and career/personal decisions
- Per-domain branch emphasis (e.g. Likely + Contrarian + Second Order for startups; all six branches for money decisions)
- Ready-made template prompts with slots for current state, constraints, exposure, and time horizon
- Explicit tensions called out (speed vs thoroughness, elegance vs shipping, risk vs opportunity cost)
- 4 domain-specific scenario template packs
- 6 analytic branches referenced for full investment/financial analysis
Adoption & trust: 536 installs on skills.sh; 27.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You face a high-stakes fork (market, stack, capital, career) but your agent analysis drifts without a shared list of variables, branches, and prompt structure.
Who is it for?
Indie founders and builders comparing paths (pricing, build vs buy, funding timing, migrations) who want agent prompts aligned to decision type.
Skip if: Teams that already have signed-off specs and only need implementation tasks, or users who want automated data pulls instead of structured scenario wording.
When should I use this skill?
Before committing to a major business, technical, financial, or career decision when you want branch-weighted what-if prompts.
What do I get? / Deliverables
You get repeatable what-if frames per domain—variables, branch weights, tensions, and filled template prompts—ready to feed into deeper analysis or planning skills.
- Domain-aligned variable list
- Branch emphasis guidance
- Filled what-if template prompt for the agent
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Frame market-entry timing and partnership terms with Likely Case and Contrarian branches before picking a niche.
Compare pricing strategy options with explicit speed-vs-thoroughness tension while runway is the constraint.
Stress-test build-vs-buy and migration paths with Worst Case and Wild Card emphasis before rewriting core services.
Revisit capital allocation and revenue-model what-ifs when exposure or horizon changes mid-run.
Use career/persona templates when hiring or role changes affect solo capacity and roadmap.
How it compares
Use as structured decision templates instead of unstructured chat speculation when stakes or second-order effects matter.
Common Questions / FAQ
Who is what-if-oracle for?
Solo and indie builders using Claude Code, Cursor, or Codex who want consistent what-if scaffolding for business, technical, financial, and career decisions.
When should I use what-if-oracle?
During validate/scope when comparing strategies; at idea/research when exploring market entry; during build when choosing architecture or migration; and at operate when reassessing runway or exposure—anytime you need branch-weighted scenarios before locking a plan.
Is what-if-oracle safe to install?
It is documentation-style procedural knowledge with no declared tool permissions in the excerpt; review the Security Audits panel on this Prism page before trusting any bundled repo skills.
SKILL.md
READMESKILL.md - What If Oracle
# 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 |