Skip to content
alyn
tjboudreaux

Thinking Effectuation skill

Under genuine uncertainty with no reliable forecast, inventory means, cap downside at affordable loss, act for commitments, and let goals emerge from controllable moves.

$npx skills add tjboudreaux/cc-thinking-skills --skill thinking-effectuation
View this skill on GitHubtjboudreaux/cc-thinking-skills/skills/thinking-effectuation/SKILL.md
Pack stars
1,724
Pack installs
20k
Alyn Score
54/99
Updated
3 months ago
License
MIT
– views – installs via Alyn

Install Thinking Effectuation

Pick your agent. Every command is ready to paste.

$npx skills add tjboudreaux/cc-thinking-skills --skill thinking-effectuation

The open skills CLI detects your agents (Claude Code, Cursor, Codex and 70+ more) and installs to the right folder. Add -g to install globally.

01

Install it

Run the command above, or upload the folder in Claude.

02

Ask naturally

Describe the task. Your agent loads thinking-effectuation when the request matches its description.

03

Name it if needed

If it does not trigger, say “use the thinking-effectuation skill”. In Codex, type $thinking-effectuation.

The skill itself

SKILL.md

FolderGitHub

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.

Tips for Thinking Effectuation

  • • Start a fresh session after installing so your agent picks up the new skill.
  • • It is part of a pack with 28 skills. Install only the ones you need with --skill to keep triggers precise.
  • • If two skills overlap, mention the one you want by name.

Questions about Thinking Effectuation

What does the Thinking Effectuation skill do?

Under genuine uncertainty with no reliable forecast, inventory means, cap downside at affordable loss, act for commitments, and let goals emerge from controllable moves.

How do I install Thinking Effectuation?

Run "npx skills add tjboudreaux/cc-thinking-skills --skill thinking-effectuation" in your project. The skills CLI installs it for Claude Code, Cursor, Codex and 70+ other agents. In Claude on the web, upload the skill folder as a ZIP under Customize > Skills.

Does Thinking Effectuation work in Cursor and Codex?

Yes. Thinking Effectuation uses the open SKILL.md format, so it works in Claude Code, Claude, Cursor, OpenAI Codex, Gemini CLI, GitHub Copilot and other agents that support agent skills.

Is Thinking Effectuation free?

Thinking Effectuation is open source on GitHub under the MIT license. It is free to install; check the license before commercial use.

Who made Thinking Effectuation?

Thinking Effectuation is published by tjboudreaux in the tjboudreaux/cc-thinking-skills repository, together with 27 other skills.

Similar skills. From other creators.