thinking-effectuation — Claude Code skill: means over forecasts
A skill for decisions under genuine uncertainty: inventory your means, then take one step inside an affordable-loss cap. Useful when forecasts can't be trusted.
npx skills add tjboudreaux/cc-thinking-skills --skill thinking-effectuation -a claude-codeWhat thinking-effectuation does
The skill pushes the agent to start from what's already at hand instead of from a fixed goal. It inventories means: who you are (skills, constraints, values), what you know (domain, tools, data), and who you can reach. An ideal plan is explicitly not an input.
Next it sets affordable loss — time, money, reputation, opportunity cost — and picks one action inside those caps. That action has to earn either a real commitment from someone or discriminating information. Feedback without commitment gets discarded. Surprises count as new means, not as a reason to restore the old plan.
You get an effectuation brief with means, affordable_loss, next_action, commitments_sought_or_won, contingencies_used, emerging_goal, and stop_or_loop. The skill checks itself: a brief that starts from a fixed goal and backfills resources gets rewritten. Where a reliable forecast and a known playbook exist, the skill tells you not to use it and to plan causally instead. Worth checking whether you actually face uncertainty or just routine execution.
What it helps with
- pick a first move when market or technology forecasts are untrustworthy
- cap time and money losses before the project starts
- tell real partner commitments apart from polite interest
- reframe a failed hire or an off-roadmap request as a new means
- stop exploring and switch back to ordinary planning
Example prompts for the agent
- Work through this new niche with effectuation: inventory my means and give me one step inside my affordable loss
- Run an effectuation brief on my project with means, affordable_loss and next_action
- My plans keep breaking — rework them through effectuation and tell me when to switch to causal planning
How to install thinking-effectuation
1Skills CLI (Vercel)
npx skills add tjboudreaux/cc-thinking-skills --skill thinking-effectuation -a claude-code2Manually: put the files in place
~/.claude/skills/thinking-effectuation/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/thinking-effectuation/
1Skills CLI (Vercel)
npx skills add tjboudreaux/cc-thinking-skills --skill thinking-effectuation -a codex2Manually: put the files in place
.agents/skills/thinking-effectuation/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add tjboudreaux/cc-thinking-skills --skill thinking-effectuation -a cursor2Manually: put the files in place
.cursor/skills/thinking-effectuation/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install tjboudreaux/cc-thinking-skills thinking-effectuation2Manually: put the files in place
.github/skills/thinking-effectuation/SKILL.md1Skills CLI (Vercel)
npx skills add tjboudreaux/cc-thinking-skills --skill thinking-effectuation -a gemini-cli2Platform CLI
gemini skills install https://github.com/tjboudreaux/cc-thinking-skills --path skills/thinking-effectuationManually: put the files in place
.devin/skills/thinking-effectuation/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add tjboudreaux/cc-thinking-skills --skill thinking-effectuation -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about thinking-effectuation
How do I install thinking-effectuation in Claude?
Run npx skills add tjboudreaux/cc-thinking-skills --skill thinking-effectuation -a claude-code. The skill lands at ~/.claude/skills/thinking-effectuation/SKILL.md.
What does thinking-effectuation do?
It moves the agent from available means to a controllable action rather than from a fixed goal to a predicted return. The output is a brief with the means inventory, loss caps, the next step, and a stop-or-loop decision.
When should I not use this skill?
When the path is predictable: known market, knowable unit economics, an established playbook. The skill itself points you to causal planning there. It also warns against affordable-loss steps when a single wrong move is irreversible.
Source text
SKILL.md · MIT
--- name: thinking-effectuation description: Under genuine uncertainty with no reliable forecast, inventory means, cap downside at affordable loss, act for commitments, and let goals emerge from controllable moves. disable-model-invocation: true --- # Effectuation Under Knightian uncertainty, start from available means and affordable loss—not a fixed goal and predicted return. Create the path through controllable action and real commitments. ## When to Use - The market, technology, or problem is novel enough that outcome probabilities are not trustworthy. - Means are clearer than the goal: identity, skills, assets, and network exist before a fixed target does. - A small action can buy information or a partner commitment without risking ruin. - Plans keep breaking because the environment shifts faster than forecasts. ## When NOT to Use - The path is predictable: known market, knowable unit economics, established playbook → use causal planning. - A single wrong step is ruinous or irreversible → de-risk first; do not treat affordable-loss steps as free. - The goal is already fixed and resources are the only uncertainty → plan to the goal. - Routine execution with settled requirements → act; do not re-inventory means. ## Procedure 1. **Inventory means only.** List who you are (skills, constraints, values), what you know (domain, tools, data), and who you know (reachable partners, users, resources). Reject "what would be needed for an ideal plan" as input. 2. **Cap affordable loss.** State the maximum time, money, reputation, and opportunity cost you can lose and still continue. If the proposed step exceeds any cap, redesign the step smaller or stop. 3. **Choose one controllable next action.** Prefer the smallest action that can yield either (a) a real commitment from someone else or (b) discriminating information. Act inside the loss cap; do not optimize expected return. 4. **Seek commitments, not opinions.** Share the working means-based offer. Anyone who commits resources, access, or work becomes a co-creator and may reshape the goal. Discard non-committing feedback as non-binding. 5. **Leverage contingencies.** Treat surprises as new means: failed hires, competitor moves, off-roadmap requests. Ask "how can this expand control?" not "how do we restore the old plan?" 6. **Update means and goal, then stop or loop.** Fold new means and commitments into the inventory; restate the emerging goal. Stop when a viable path is controlled enough to execute, the loss cap is exhausted without traction, or uncertainty collapses into a predictable plan (then switch to causal planning). ## Output Emit an effectuation brief: - `means`: identity / knowledge / network actually available now - `affordable_loss`: hard caps (time, money, reputation, opportunity) - `next_action`: one controllable step inside those caps - `commitments_sought_or_won`: who must put skin in the game, and what changed if they did - `contingencies_used`: surprises turned into means (or none) - `emerging_goal`: current goal shaped by means and commitments (may differ from the starting wish) - `stop_or_loop`: continue under effectuation, switch to causal planning, or halt ## Verification - **Falsify means-first claims:** if the brief starts from a fixed goal and backfills resources, rewrite from means or abandon effectuation. - **Loss-cap check:** every recommended action must fit inside stated affordable loss; if not, shrink or stop. - **Commitment test:** progress that depends only on predictions or uncommitted interest is invalid—require at least one real commitment or a cheap information gain. - **Over-application guard:** if a reliable forecast and known playbook exist, do not force effectuation; plan causally. - **Stop:** after one means → loss-cap → action → commitment cycle with an explicit stop/loop decision; do not endless-explore under the effectuation label.
© tjboudreaux · MIT · tjboudreaux/cc-thinking-skills