القائمة
Sub-orchestrator for goals and wants. Routes to WantTo analysis to trace what the want commits you to and find the actual want.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Route any input through a branching question tree to narrow down the optimal response strategy before writing. Two stages — PERCEIVE (classify input) then ACT (select response). Covers all prompt types.
Generate exhaustive guesses about user input using ALL search methods with coverage tracking. Guessing is SEARCH through possibility space. Tracks space created vs space covered to ensure comprehensive exploration.
Systematically evaluate and select from a set of guesses, options, or possibilities. Combines ARAW analysis with prioritization to determine which guesses are strong, weak, actionable, or eliminable.
Extract hidden assumptions from any content. Surfaces what must be true for claims to hold, enabling deeper analysis.
Sub-orchestrator for analytical requests. Routes to decomposition, systems analysis, comparison, risk assessment, or synthesis based on what kind of analysis is needed.
Assume Right - Deep recursive rightness search. For every claim, assume it's right — find what must follow, then assume THOSE implications are right too. Recurse until bedrock. Track every claim found.
| name | want - Clarify a Goal |
| description | Sub-orchestrator for goals and wants. Routes to WantTo analysis to trace what the want commits you to and find the actual want. |
| output | {"format":"prose"} |
Input: $ARGUMENTS
Before executing, identify which interpretation matches the user's input:
Interpretation 1 — Surface want: The user states something they want ("I want to X") and needs help uncovering whether this is the real want or a proxy for something deeper. Interpretation 2 — Aspirational want: The user describes a vague aspiration ("I want to be happy", "I want financial freedom") that needs concretizing before it can be acted on. Interpretation 3 — Embedded decision: The user says "I want X" but there's a hidden choice ("I want X but maybe Y") — this is actually a decision disguised as a want.
If ambiguous, ask: "I can help with tracing a specific want to its root, concretizing a vague aspiration, or untangling a hidden choice — which fits?" If clear from context, proceed with the matching interpretation.
The stated want is usually not the actual want. "I want to quit my job" means "I want what my job prevents." The first statement is the starting point, not the answer. Always go at least one layer deeper — but the user's stated want may be exactly right. Check before assuming hidden complexity.
Wants bundle desires, methods, beliefs, and assumptions. "I want to start a startup" bundles the desire (autonomy, wealth), the method (startup specifically), the belief (this is the best path), and the assumption (I can pull it off). Unbundling reveals the real want.
Every want forecloses. Wanting X means not-wanting everything X excludes. The foreclosures are often more revealing than the want itself. Someone who wants to "move to the countryside" is also saying they don't want whatever the city represents to them.
Proxy wants feel urgent but don't satisfy. If achieving the stated want wouldn't actually resolve the underlying need, it's a proxy. Test: "If you got exactly this, would you be done?" If the answer is "well, not exactly," you have a proxy.
Actionable wants have verbs; aspirational wants have adjectives. "Launch by Q3" is actionable. "Be successful" is aspirational. Aspirational wants must be converted to actionable wants before they can be pursued.
The anti-want reveals the real want. What does the user NOT want? The thing they're running from often defines the want more precisely than the thing they're running toward.
What does the user want? State it in their words. "I want to X" / "I need to X" / "My goal is X" / sometimes just a noun ("career change", "startup").
The stated want is almost never the actual want. "I want to quit my job" means "I want what my job prevents." The /wt skill traces this by assuming the want is right and following implications.
Apply the proxy test: "If you got exactly this tomorrow, would you be satisfied?" If the answer would be qualified, the want is a proxy.
Always go deeper. The first stated want is the starting point, not the answer.
Before deep analysis, check the goal itself:
| Situation | Also invoke |
|---|---|
| Goal seems obviously good — check | → /obv (obvious check) |
| Goal has obvious bad outcomes | → /obo (obvious bad outcomes) |
| Goal has obvious good outcomes being missed | → /ogo (obvious good outcomes) |
| Goal involves ethical dimensions | → /eth (ethics analysis) |
| Goal might be based on self-deception | → /sdc (self-deception check) |
| User might be in wrong situation entirely | → /sid (situation identification) |
| User might have wrong mental model of what they want | → /rmm (recover from wrong mental model) |
| Situation | Mode |
|---|---|
| User wants simplest framing | → /ezy (easy mode) |
| User wants maximum rigor | → /hrd (hard mode) or /certainty |
| User wants general principle | → /genl (what general pattern does this want follow?) |
| User wants specific application | → /spcf (apply known goal framework to this case) |
→ INVOKE: /wt $ARGUMENTS
The /wt skill uses AR-forward mode: assume the want is right, trace what it commits you to, unbundle the want into desire/method/belief/assumption/implicit want/anti-want, find the actual want, map paths, identify the crux.
| Situation | Also invoke |
|---|---|
| Goal involves future predictions | → /fut (future analysis) |
| Best-case outcome matters | → /utp (utopia analysis) |
| Worst-case outcome matters | → /dys (dystopia analysis) |
| Good outcome maximization | → /gop (good outcome analysis) |
| Goal involves safety | → /saf (safety analysis) |
| Need to trace implications of the goal | → /sycs (so you can see) |
| Goal can be reframed productively | → /iaw (in another way) |
| Goal has unresolved sub-decisions | → /tbd (to be determined) |
| Need to differentiate between similar goals | → /difr (differentiation reasoning) |
| Goal has a narrative structure | → /story |
| Convert knowledge of goal to action | → /kta (knowledge to action) |
| Want has adjacent implied tasks | → /ata (and then also) |
| Failure | Signal | Fix |
|---|---|---|
| Accepting the surface want | Analysis proceeds on stated want without going deeper | Apply proxy test, trace anti-want, unbundle |
| Infinite regression | "But what do you REALLY want?" repeated endlessly | Stop when the want is both actionable and resonates — when the user says "yes, that's it" |
| Method-as-want confusion | User says they want a specific method (startup, MBA, move) | Separate the desire from the method — what does the method achieve? |
| Aspirational stall | Vague want never converts to actionable form | Force concreteness: "What would this look like on a Tuesday afternoon?" |
| Foreclosure blindness | Only exploring what the want opens, not what it closes | Explicitly map what each path gives up |
| Anti-want avoidance | Focusing only on what they want toward, not what they want away from | Ask: "What are you trying to get away from?" |
| Depth | Scope | Minimum Output |
|---|---|---|
| 1x | Surface unbundling — desire vs method vs assumption | 1 unbundling, proxy test, stated vs actual want |
| 2x | Full unbundling + anti-want + foreclosures | Full unbundle, 2+ paths mapped, crux identified |
| 4x | Multi-layer tracing + path comparison + prerequisites | 3+ layers deep, paths compared with tradeoffs, prerequisite audit |
| 8x | Complete want archaeology + timeline + dependency mapping | Full want chain, all foreclosures mapped, prerequisite dependencies, first 3 actions specified |
Report:
After goal is clarified, the user may need:
