MCPInstall

thinking-opportunity-cost

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.

Installs
616
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/tjboudreaux/cc-thinking-skills --skill thinking-opportunity-cost
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads thinking-opportunity-cost automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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

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.

FAQ

What does the thinking-opportunity-cost skill do?

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.

How do I install thinking-opportunity-cost?

Run npx skills add https://github.com/tjboudreaux/cc-thinking-skills --skill thinking-opportunity-cost in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/thinking-opportunity-cost/ (personal) or .claude/skills/thinking-opportunity-cost/ (project).

Which AI agents can use thinking-opportunity-cost?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is thinking-opportunity-cost safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains thinking-opportunity-cost?

It is published by tjboudreaux in tjboudreaux/cc-thinking-skills. It has 616 recorded installs.

More from tjboudreaux/cc-thinking-skills

View all →

thinking-first-principles

tjboudreaux/cc-thinking-skills

When a constraint is treated as fixed, separate physics from convention, keep only independently supported primitives, and rebuild the simplest solution that satisfies real constraints.

thinking-red-team

tjboudreaux/cc-thinking-skills

For authorized security review of code, auth, or APIs you control, model the attacker, map the attack surface, and report only findings with a reproducible exploit path and verified mitigation.

Backend & APIs674 installs

thinking-pre-mortem

tjboudreaux/cc-thinking-skills

Before committing to a plan or launch, assume it already failed and reason backward through concrete causes — convert failure paths into mitigations, gates, and stop checks.

thinking-theory-of-constraints

tjboudreaux/cc-thinking-skills

When throughput or latency is pipeline-limited, identify the single binding constraint and exploit, subordinate, elevate, then recheck—ignore non-constraints.

649 installs

thinking-socratic

tjboudreaux/cc-thinking-skills

When a request is vague, assumption-laden, or "obvious," ask the few load-bearing questions that expose hidden requirements before building or committing.

631 installs

thinking-systems

tjboudreaux/cc-thinking-skills

When behavior is emergent across components—fixes elsewhere break, loops/delays dominate—map boundary, stocks/flows, feedback, archetypes, then rank leverage.

615 installs

Popular other skills

View category →

hyperframes-cli

heygen-com/hyperframes

The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.

1.3M installs

triage

mattpocock/skills

Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

1M installs

ask-matt

mattpocock/skills

Ask which skill or flow fits your situation. A router over the skills in this repo.

778.4K installs

to-questionnaire

mattpocock/skills

Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

508.9K installs

wait-what

mattpocock/skills

Stop. That last message did not land: re-pitch it.

459.7K installs

loop-me

mattpocock/skills

Grill me about specs for the workflows I want to build, within this workspace.

447.9K installs