Thinking Effectuation

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 9a5557e61022 · 27 Oct 2026Report an issue or request a re-scan

• Publishertjboudreaux GitHub userOwner of the repository this skill is read from
• Source foldertjboudreaux/cc-thinking-skills/skills/thinking-effectuationThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict9a5557e61022A new audit runs when the source changes
• Repository statusNot archivedLast push 80 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its 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.

---
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.

Excerpt, first 3,905 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/tjboudreaux/cc-thinking-skills
git -C cc-thinking-skills checkout 9a5557e61022

Works in

1. 2026-10-27
   ✓SAFE B 89 / 100

   first audit · source 9a5557e61022

Questions about Thinking Effectuation

• github.com/tjboudreaux/cc-thinking-skills/tree/main/skills/think — the audited source at commit 9a5557e61022 and every finding aboveObserved · 27 Oct 2026

Spotted something wrong? Report a correction · Methodology