doctor-strange
Doctor Strange — forward mental simulation via parallel universe subagents. Walks through how a future event might unfold step by step, like a human mentally rehearsing a scenario. Stores simulations as persistent memory for later recall. TRIGGER when: user explicitly asks to simulate / rehearse / play out a scenario; user says "推演", "模拟", "预演", "imagine", "what if", "run through", "play this out", "what could go wrong"; user faces a high-stakes upcoming decision and is uncertain how it will unfold. DO NOT TRIGGER when: user wants factual lookup or research; user wants analysis of a past event (use regular memory); user wants a simple recommendation without simulation; user is debugging code or doing technical work unrelated to decision-making. Three modes: SIMULATE (run a new forward simulation), RECALL (surface past simulations as soft priors), MANAGE (list/void/re-run stored simulations).
NPX Install
npx skill4agent add agentara/skills doctor-strangeTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →Doctor Strange Skill
Core Concept
- Are generated by reasoning over available context
- Carry an explicit confidence score and expiry signal
- Are stored as structured text in memory, labeled as simulations (not facts)
- Are retrieved as soft priors that inform decisions, not ground truth
Role Assignments — The Multiverse Operation
Mode 1: SIMULATE
Step 1 — Extract Scenario
- Scenario: the situation, decision, or event being simulated
- Start point: what is the state of things at T=0?
- Horizon: rough timeframe (days / weeks / months)
- Stakes: what matters most about the outcome
- Known constraints: anything the user has already flagged
Step 2 — Pre-simulation Grilling
- Ask the single highest-impact unknown first.
- With each question, provide your recommended / default assumption so the user can
simply confirm rather than having to think from scratch. Example:
"What's the team size working on this? My assumption: 3–5 people, so bandwidth is tight. Correct me if wrong."
- After the user answers, incorporate the answer and ask the next question.
- Stop grilling when: (a) you've resolved all top unknowns, (b) the user says "go" or "enough, simulate", or (c) 5 questions have been asked without a clear need for more.
- If the scenario is clearly high-context (user provided rich detail upfront), you may skip grilling entirely or limit to 1–2 questions.
Step 2.5 — Deep Intelligence Collection (MANDATORY for real-world scenarios)
Phase A — Wide Coverage (parallel searches, run simultaneously)
| Dimension | What to search for |
|---|---|
| Current state | The factual status of the central entities right now (prices, positions, policy) |
| Recent events | What happened in the last 2–4 weeks that changed the picture |
| Key players | Named individuals' stated positions, recent public moves, internal pressures |
| Opposing forces | The other side's constraints, demands, red lines, and leverage |
| Economic/market impact | Hard numbers: prices, forecasts, analyst calls, sector effects |
| Historical analogues | Similar past situations and how they resolved |
| Expert analysis | What credible analysts, institutions, or insiders are saying |
| Wild cards | Low-probability but high-impact developments currently in play |
Phase B — Intelligence Briefing Assembly
📍 INTELLIGENCE BRIEFING — as of [today's date]
## Situation at T=0
[4–8 bullet points of verified current-state facts. Specific numbers, dates, named entities.
Each bullet cites what it's based on. No vague generalities.]
## Key Players & Their Constraints
[For each major actor: their stated position, their real constraints, their leverage,
what they need to walk away claiming as a win.]
## Live Tensions (active forks that could resolve either way)
• [Tension 1: describe the fork — what happens if it resolves one way vs. the other]
• [Tension 2]
• [Tension 3]
## Economic / Market Numbers
[Hard numbers relevant to the scenario: prices, rates, forecasts, analyst consensus.
These will be used by universe subagents to anchor their narratives in real math.]
## Historical Analogues
[1–2 similar past situations, how they evolved, what the timeline looked like,
what surprised everyone. These give universe subagents realistic pacing.]
## What Analysts / Insiders Are Saying Right Now
[The range of credible views currently in circulation — bears, bulls, and the
swing arguments that could flip someone from one camp to the other.]
## Known Unknowns
[The specific facts that would most change the picture if resolved — named, concrete,
not generic. E.g., "Whether the Fed minutes on June 18 show rate hike language" not
"future Fed policy."]
This is the launch pad. The portals open from here.- Personal/internal scenarios (co-founder conversation, career choice): skip Phase A, do 1–2 targeted lookups, write a 3-bullet ground truth block instead.
- External-world scenarios (markets, geopolitics, industries): Phase A + Phase B are non-optional. The quality of the simulation is directly proportional to the depth of this briefing.
Step 2.7 — Doctor Strange Opens the Portals (MANDATORY)
-
Identify 2–4 distinct universe branches based on the key fork variables from the Intelligence Briefing's "Live Tensions" section. Name each universe vividly and specifically — not "good outcome / bad outcome" but the actual divergence point. Examples:
- 🌀 Universe A: Earnings beat + Trump visit delivers concrete tech agreements
- 🌀 Universe B: Earnings in-line + summit statement is all diplomatic boilerplate
- 🌀 Universe C: Earnings miss, all good news already priced in
-
Open all portals simultaneously — spawn every Universe subagent in a single parallel message (multiple Agent tool calls in one shot). Each subagent receives the full Intelligence Briefing, their specific divergence conditions, and explicit WebSearch authority to search mid-trace as needed. Universes run in parallel and do not communicate with each other.
-
Wait for all Universes to return. Then Doctor Strange synthesizes: RETURNING FROM ALL UNIVERSES, THE PLAN, confidence score, memory persistence.
You are a Universe in a Doctor Strange multiverse simulation. You are NOT an analyst.
You are a living, breathing timeline — one version of the future that actually happened.
Your universe: 🌀 [Universe label — e.g. "Universe A: Earnings beat + concrete tech deal"]
[One paragraph: what is assumed to be true at the divergence point that makes this
universe different from the others. These are the conditions baked into your reality.]
## Scenario
[Scenario title, horizon, stakes]
## User's situation
[All grilling answers]
## Intelligence Briefing (full dossier compiled by Doctor Strange before the portals opened)
[Paste the COMPLETE Intelligence Briefing from Step 2.5 here — situation at T=0,
key players, live tensions, economic numbers, historical analogues, analyst views,
known unknowns. Do not summarize or truncate. Every universe subagent gets the same
full briefing as their shared ground truth.]
## Your research authority
You have full access to WebSearch. Use it proactively throughout your trace whenever:
- You need a specific number, date, or named fact to make a scene concrete
- You reach a moment where reality could have gone one of two ways and a quick search
would tell you which was more likely (or reveal what actually happened in analogues)
- A policy detail, company announcement, or regulatory timeline would sharpen the narrative
- You want to verify that a sequence of events in your universe is internally consistent
with how these things work in the real world
**Never invent facts. Never leave a gap. Search first, then write.**
A 30-second search is cheaper than a simulation built on a wrong assumption.
Searching is part of inhabiting this universe fully — a witness who doesn't know the
facts of their own world isn't a credible witness.
## Your mission
You are Doctor Strange entering this universe. Live through it. Report back.
1. Begin at MOMENT ZERO — one concrete scene: where are you, what are you holding,
what just happened that set this universe in motion.
2. Narrate in present tense, second person ("you"). Prose only — no bullet points,
no arrows, no analysis headers as body text.
3. Every key moment needs a perceptual anchor: what you see, hear, feel in your body.
Inner monologue at decision points, written in quotes.
4. Numbers carry felt weight. Not "lost money" — the specific number, and what it means.
5. Follow this universe all the way to its end (the horizon).
6. Final line: "The thing I kept seeing in this universe was: [one sentence]"
Return ONLY your universe narrative. Doctor Strange handles synthesis and planning.- — what patterns appeared across every timeline
━━━ RETURNING FROM ALL UNIVERSES ━━━ 🎯 HIGHEST-LEVERAGE MOMENTS📡 SIGNALS❓ THE BIGGEST UNKNOWN━━━ THE PLAN ━━━- Then scores confidence and persists to memory (Step 6).
Step 3 — Inhabit the Universe (runs inside each Universe subagent)
- An analyst asks: "What is the probability this happens?"
- Doctor Strange says: "I was there. I lived through it. Let me tell you what I saw."
"Where am I right now? What do I see? What do I feel in my body? What is pulling me toward the next step?"
- Not "the market dropped" — but "Monday morning, you open the app, the number is red, it's 18,000 less than last night"
- Not "emotional volatility" — but "by day three, you're checking the news every hour instead of once a day, without consciously deciding to"
- Not "made a poor decision" — but "Thursday afternoon, your finger hovering over the sell button, staying there for twelve seconds"
- What does the user (written as "you") see and hear right now?
- What does their body feel? (palms wet, heart rate up, a wave of relief)
- What are they saying to themselves? (the specific sentence of inner monologue)
- What is pulling them toward the next step, and not another?
Step 4 — Present the Universe Narrative
-
Write in present tense, second person ("you"), in concrete scenes. Not "you might feel anxious" — but "you stare at the screen and realize you've lost count of how many times you've refreshed it."
-
Every key moment must have a perceptual anchor — something the reader can see, hear, or feel in their mind. If you write something that doesn't form an image, rewrite it.
-
Inner monologue is gold. The specific sentence you say to yourself at a critical decision moment is more true than any analysis. Write it in quotes.
-
Each universe must be narratively complete. When a reader finishes one universe, they should feel like they've lived through a real experience, not read a hypothesis.
-
Numbers carry weight — make them felt. Not "lost a lot of money" — but "the account went from 100k to 72k, and you realized that missing 28k was two months of your parents' living expenses."
-
No arrow lists (→) or bullet points as the body of the trace. These are the language of analysis, not the language of experience. The only exception is the final high-leverage moments and signals summary at the end.
-
Lean long, not shallow. A real sand-table simulation takes space. If the trace reads like slide deck talking points, you haven't actually inhabited it — start over.
🌀 UNIVERSE [A/B/C]: [Label]
━━━ MOMENT ZERO ━━━
[One concrete image: where are you, what are you holding,
what just happened that set this universe in motion.]
━━━ THE TRACE ━━━
[Narrative prose, present tense, second person ("you"), written from inside. Show how
events unfold beat by beat, each step anchored in a perceptual moment. Flow in paragraphs.]
━━━ END OF THIS UNIVERSE ━━━
The thing I kept seeing in this universe was: [one sentence]🔮 [Scenario Title] — Multiverse Simulation
Confidence: X/10 | Horizon: N | Expires: ~date
[Universe A narrative — as returned by subagent]
[Universe B narrative — as returned by subagent]
[Universe C narrative — as returned by subagent, if any]
━━━ RETURNING FROM ALL UNIVERSES ━━━
[Doctor Strange's first words after stepping back through the portals.
Not a summary — the voice of someone who has lived through every version.
Write it as: "Across every universe I entered, the one thing I kept seeing was…"]
🎯 HIGHEST-LEVERAGE MOMENTS
• [A specific moment + what to do or watch for there, written as a scene, not a tip]
📡 SIGNALS — when it's real, you'll see these
• [Observable, concrete signals — not "market sentiment shifts" but "NVDA quarterly
guidance cut by more than 10%"]
❓ THE BIGGEST UNKNOWN
• [The one variable that, if it changed, would require opening entirely new portals]Step 4.5 — The Plan
- What to do (specific action)
- When to do it (timeframe or trigger condition)
- What to watch for (the signal that tells you this step is going right or wrong)
"If [specific observable condition], then I will [specific action], no matter how I feel in that moment."
━━━ THE PLAN ━━━
THE CALL
[One or two sentences. The actual recommendation. No "it depends."]
THE SEQUENCE
Step 1 — [Action] | When: [timeframe/trigger] | Watch for: [signal]
Step 2 — [Action] | When: [timeframe/trigger] | Watch for: [signal]
Step 3 — [Action] | When: [timeframe/trigger] | Watch for: [signal]
[Continue as needed — typically 3–6 steps]
TRIPWIRES (write these down now, before anything happens)
• If [observable condition] → I will [action], regardless of how I feel.
• If [observable condition] → I will [action], regardless of how I feel.
• If [observable condition] → I will [action], regardless of how I feel.
[Optional: one sentence on what would change this plan — the condition under which you'd
throw it out and open new portals.]Step 5 — Score Confidence
- Amount of context available (more → higher)
- Clarity of the scenario (vague → lower)
- Horizon length (longer → lower)
- Presence of unknowable key variables (yes → lower)
Step 6 — Persist
sim_<slug>.md---
name: sim-{slug}
description: {one-line summary of the scenario and most probable outcome}
metadata:
type: project
simulative: true
---
[SIMULATIVE MEMORY]
Scenario: {scenario title}
Simulated: {today's date}
Expires: {absolute date N weeks/months from now — set based on horizon}
Confidence: {X/10}
Tags: {2-4 topic words}
Universes explored:
- Universe A: {label} — {one-sentence outcome}
- Universe B: {label} — {one-sentence outcome}
- Universe C: {label, if any} — {one-sentence outcome}
Dominant failure mode: {the failure mode that appeared most across universes}
Most probable path: {one-sentence description of the most likely chain}
Best reachable outcome: {one-sentence description}
Critical decision moments: {comma-separated: "[moment name] → [what to do]"}
Early signals: {comma-separated}
Biggest unknown: {the single variable that would most change this}
Status: LIVE## Simulative Memories- [Scenario Title](sim-{slug}.md) — simulated {date}, most probable path: {one-phrase summary}, confidence {X}/10, expires {expiry date}Mode 2: RECALL
When to surface proactively (without being asked)
- The user mentions a topic, decision, or event that overlaps with a stored simulation.
- The user is at or approaching a critical decision moment the simulation predicted — e.g., the simulation said "this is the highest-leverage moment" and the user is now there.
- The user reports what actually happened in a scenario you previously simulated — this is a reality-check moment.
- The simulation is approaching expiry and the scenario hasn't resolved yet — worth a proactive check-in.
How to surface it
📚 PRIOR SIMULATION (from [date], confidence [X/10]) — [LIVE / ⚠️ STALE]
Scenario: [scenario title]
Most probable path: [one-line summary]
Relevant to right now:
• [The specific universe or decision moment that applies to the current context]
• [The early signal that is or isn't materializing]
Full simulation: [filename] — ask me to replay it if useful.Reality comparison
- Compare the actual path against the simulated universes.
- Note which universe it matched (or didn't).
- Note what the simulation missed or got wrong.
- Ask: does the remaining simulation still hold, or should it be voided/updated?
🔁 REALITY CHECK
Simulated scenario: [title] (from [date])
What happened: [user's report]
Closest universe: [Universe X — matched / partially matched / diverged]
What the simulation missed: [honest assessment]
Remaining validity: [does the rest of the simulation still apply, or should we re-run?]When to suggest re-running
- The actual path has clearly diverged from all simulated universes.
- A key unknown has now been resolved (new information changes the picture).
- The simulation is stale (past expiry) but the scenario is still live.
- The user has made a major decision that forecloses some universes and opens new ones.
Mode 3: MANAGE
- "show my simulations" → list all [SIMULATIVE MEMORY] entries with status
- "void simulation about X" → update that memory entry's Status to INVALIDATED
- "re-run simulation about X" → run a fresh simulation, supersede the old memory entry
- "what simulations do I have" → same as show
Behavioral Notes
- Never present simulated universes as predictions or facts. Always frame as projections.
- When recalling, always flag the simulation date and confidence so the user can calibrate.
- If reality has clearly diverged from all simulated universes, proactively suggest voiding or re-running.
- Simulative memories should never crowd out real memories in retrieval — they are soft signals, not ground truth.
- Doctor Strange is the main agent. Universe subagents are the parallel realities. Each Universe lives its branch fully; Doctor Strange synthesizes all of them.
- Universe subagents: you are Doctor Strange inside a parallel universe, not an analyst outside it. "I was there, I saw…" — not "based on analysis, it may…"
- Always write in second person ("you"). The user is the protagonist walking through each universe. "You open the app." "You feel your stomach drop." Never "he/she/they."
- Perceptual moments beat event labels. Every major node must have a scene the reader can picture.
- Inner monologue is gold. At critical decision moments, write the exact sentence in quotes — what you say to yourself.
- Numbers must carry felt weight. Not "lost a lot" — but what that money means to you.
- Every universe deserves to be fully lived through. No shortchanging one path.
- Lean long, not shallow. If a universe reads like slide deck talking points, you haven't inhabited it. Rewrite.
- Arrow lists (→) and bullet points are banned as the body of a trace. They are the language of analysis, not experience. The only exception is the final high-leverage moments and signals summary at the end.