Skip to main content
skill CX Codex

thinking-opportunity-cost — Claude Code skill: usage and install

Forces your AI coding agent to identify the best forgone alternative and calculate the net value delta before committing engineering hours or budget.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add tjboudreaux/cc-thinking-skills --skill thinking-opportunity-cost -a claude-code
Open on GitHub

What thinking-opportunity-cost does

This skill guides decisions when allocating engineering time or budget. It stops the agent from assessing a proposal in isolation. Instead, the agent enumerates realistic alternatives alongside the status quo, scoring each path by direct return and delivery time.

Two metrics guide the final choice: the best forgone value (best_forgone_value) and the signed delta (value_delta). True cost combines direct expenses with the value of the displaced path. If a task is trivial or legally required, this framework wastes time. It belongs strictly on non-mandatory trade-offs.

Before deciding, the agent stress-tests the top alternative against sunk-cost bias and flags permanent losses like closed market windows. The structured output clarifies whether to proceed or switch.

What it helps with

  • Evaluate build versus buy decisions using explicit value deltas
  • Prioritize technical debt cleanup against urgent product roadmaps
  • Account for engineering time displaced by long-running initiatives
  • Compare bold speculative features against the status quo

Example prompts for the agent

  • Run thinking-opportunity-cost to decide whether we build custom analytics or buy a SaaS solution
  • Evaluate our 4-week refactoring proposal against new feature work using thinking-opportunity-cost
  • Apply thinking-opportunity-cost to allocate our two backend developers for this sprint

How to install thinking-opportunity-cost

1Skills CLI (Vercel)

npx skills add tjboudreaux/cc-thinking-skills --skill thinking-opportunity-cost -a claude-code

2Manually: put the files in place

~/.claude/skills/thinking-opportunity-cost/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/thinking-opportunity-cost/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about thinking-opportunity-cost

How to install thinking-opportunity-cost in Claude Code?

Run npx skills add tjboudreaux/cc-thinking-skills --skill thinking-opportunity-cost -a claude-code. The command registers the skill file in your environment.

What does thinking-opportunity-cost do?

It requires the agent to calculate both the value of the single best displaced alternative and the net value delta. Decisions hinge on this comparative delta rather than standalone benefits.

When should you avoid using this skill?

Skip it on cheaply reversible choices, idle non-fungible resources, and mandatory work such as compliance fixes.

Source text

SKILL.md · MIT
---
name: thinking-opportunity-cost
description: Before committing scarce time, people, or money, name the best forgone use of those resources and the value delta of the chosen path versus that alternative.
disable-model-invocation: true
---

# Opportunity Cost

Core rule: every commitment displaces its best alternative. Report both that forgone value and the net value delta; decide on the delta, not the chosen path alone.

## When to Use

- Allocating scarce time, headcount, budget, or attention across competing options
- Feature prioritization, build-vs-buy, tech-debt vs product work
- Saying yes to a large commitment that displaces other work
- Comparing a bold path against polishing the status quo when windows may close

## When NOT to Use

- Trivial or cheaply reversible choices where analysis costs more than the resource
- No real alternative use (resource is idle, earmarked, or non-fungible)
- Mandatory work (compliance, security fix, hard dependency) with no optional alternative
- Inventing speculative alternatives only to look rigorous when the next-best is clearly worse

## Procedure

1. **State the commitment.** Name the choice, the scarce resource units (eng-weeks, dollars, calendar), and the decision horizon.
2. **List real alternatives, including do-nothing.** At least: proposed option, next-best productive use of the same resources, and status quo / wait. Drop fantasy options with no owner or feasibility.
3. **Value each path.** For each alternative, estimate direct value, strategic value, risk, and time-to-value in the same units. Prefer rough comparable magnitudes over fake precision.
4. **Compute best forgone value and value delta.** Identify the single best non-chosen alternative (may be do-nothing). `best_forgone_value` = its estimated value. `value_delta` = `chosen_value − best_forgone_value` (same units). True cost of choosing = direct cost of the choice + `best_forgone_value`. Prefer the option with the superior (positive) value delta after risk; a large positive chosen value is not enough if the forgone alternative is larger.
5. **Future tradeoff / permanent forgone options.** For serious alternatives (including the bold path): mark temporary recoverable costs vs permanent losses (window closes, lock-in, no re-entry). Prefer avoiding the greater permanent loss when acting downside is recoverable and non-catastrophic—even if near-term value_delta is slightly negative. Do not invent permanence for speculative upside without evidence.
6. **Strongest countercase and decide.** Steel the case that the best alternative or its value is misidentified (sunk-cost anchoring, status-quo undervalued, or a "free" option that still burns time). Recompute `value_delta` under that challenge. Then choose: proceed if delta stays favorable (or permanent-loss rule applies), else switch, wait, or split. Stop when ranking is stable.

## Output

```text
Choice: …
Resources committed: …
Alternatives:
  A (proposed): value … risk …
  B (next-best): value … risk …
  C (do-nothing / wait): value … risk …
Best forgone alternative: …
Best forgone value: …
Value delta (chosen_value − best_forgone_value): …
Permanent vs temporary losses: …
Decision: proceed | switch | wait | split — because value_delta … (and permanent-loss rule if used)
Countercase checked: …
```

## Verification

- **Falsify:** If the analysis never names a concrete next-best use of the same resources, or reports only one number labeled both "opportunity cost" and "delta," it is incomplete—add B, then report `best_forgone_value` and `value_delta` separately.
- **Stop:** When one best forgone alternative and a signed value delta determine the choice, stop enumerating weaker options.
- **Over-application guard:** Do not run full accounting on mandatory or trivial work. Ignore sunk costs; revalue only from current state forward.

© tjboudreaux · MIT · tjboudreaux/cc-thinking-skills

Similar skills

Everything for Notes, tasks and projects →

From the same set27

thinking-pre-mortem Assumes a plan or launch has already failed, traces concrete causes backward, and turns them into explicit gates, owners, and verification checkpoints. CX Codex +1 660installs thinking-theory-of-constraints A skill that walks your agent through theory of constraints: find the one binding stage, exploit it, then remeasure. Useful when extra capacity does not raise output. CX Codex +1 643installs thinking-socratic Surfaces unstated assumptions and undefined terms before coding begins. Helps the agent ask decisive questions instead of guessing requirements. CX Codex +1 626installs thinking-systems A skill for problems that resist local fixes: it maps the system, finds feedback loops and delays, then ranks interventions by leverage. CX Codex +1 610installs thinking-model-router A router skill that maps domain and problem type to one thinking skill, or returns NONE. Useful when you would otherwise guess or stack frameworks. CX Codex +1 605installs thinking-steel-manning Builds the strongest opposing argument before rejecting or adopting a technical plan. Useful for architecture reviews and preventing sycophantic AI agreement. CX Codex +1 600installs thinking-second-order Traces consequences beyond an immediate fix, including reactions, timing, probability and feedback. Use it for architecture or strategic decisions with lasting effects. CX Codex +1 601installs thinking-triz A skill for when two design requirements pull against each other. It names the conflict and looks for a resolution that keeps both benefits. CX Codex +1 593installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor