Skip to content
alyn
tjboudreaux

Thinking Kepner Tregoe skill

Use when a selective defect needs IS/IS-NOT difference analysis or a consequential option choice needs must/want weighting and adverse-consequence comparison.

$npx skills add tjboudreaux/cc-thinking-skills --skill thinking-kepner-tregoe
View this skill on GitHubtjboudreaux/cc-thinking-skills/skills/thinking-kepner-tregoe/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 Kepner Tregoe

Pick your agent. Every command is ready to paste.

$npx skills add tjboudreaux/cc-thinking-skills --skill thinking-kepner-tregoe

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-kepner-tregoe when the request matches its description.

03

Name it if needed

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

The skill itself

SKILL.md

FolderGitHub

Kepner-Tregoe Analysis

Core rule: Diagnose deviations by testing causes against both IS and IS-NOT. Compare consequential choices by screening MUSTs, weighting WANTs, and exposing adverse consequences before selecting.

When to Use

  • A defect affects some objects, places, times, or cohorts but not comparable others.
  • Several candidate causes remain and the contrast boundary can discriminate them.
  • A consequential option choice has explicit non-negotiables, competing objectives, and risks that should be compared consistently.

When NOT to Use

  • A uniform failure has no meaningful IS-NOT contrast, or the cause is already confirmed.
  • One cheap observation settles the cause or one option plainly dominates every requirement.
  • The criteria cannot be made operational; clarify them before assigning weights.
  • The task is forward failure discovery for a planned change rather than diagnosis or option selection.

Procedure

  1. Choose the mode. Use Problem Analysis for a deviation from expected behavior; use Decision Analysis for a choice among options. State the target and do not mix scores with causal evidence.
  2. Frame the target. For a deviation, record object, defect, location, time, extent, and impact. For a choice, state the decision, alternatives, constraints, and deadline.
  3. Problem Analysis — build IS/IS-NOT. For WHAT, WHERE, WHEN, and EXTENT, record IS, closest comparable IS-NOT, and the distinction unique to the IS side. List changes near the first occurrence.
  4. Problem Analysis — difference-test causes. Generate candidates from distinctions and changes. A candidate survives only if it explains both IS and IS-NOT. Run the cheapest discriminating check; stop when one verified cause explains the full boundary.
  5. Decision Analysis — screen and score. Define pass/fail MUSTs and weighted WANTs (1–10 importance) before scoring. Eliminate options that fail any MUST; score survivors against each WANT and calculate weighted totals using the same scale.
  6. Decision Analysis — test downside and sensitivity. For leading options, list adverse consequences with probability × impact and identify assumptions or weight changes that would reverse the ranking. Do not let a high total conceal a ruinous failure mode.
  7. Decide or expose the gap. Return the verified cause or highest-ranked acceptable option, the evidence/score behind it, residual risk, and next verification. If no cause verifies or no option passes MUSTs, return open/none rather than force a winner.

Output

Return one mode-specific decision artifact:

  • Problem Analysis: problem statement; IS/IS-NOT matrix with distinctions; nearby changes; candidate-vs-boundary tests; confirmed cause or next discriminating check.
  • Decision Analysis: decision statement; alternatives; MUST screen; weighted WANT matrix; adverse-consequence table; sensitivity/reversal conditions; selected option or none.

Verification

  • Falsify/stop: reject a cause that cannot explain both sides of the boundary. Reject a choice if it fails a MUST, depends on inconsistent scoring, or loses under a plausible weight/risk change that was hidden.
  • Over-application guard: skip the full matrix for an obvious cause, trivial choice, or one-shot check. Stop when the cause verifies or the option is robust enough for the stated stakes; extra rows are ceremony.

Tips for Thinking Kepner Tregoe

  • • 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 Kepner Tregoe

What does the Thinking Kepner Tregoe skill do?

Use when a selective defect needs IS/IS-NOT difference analysis or a consequential option choice needs must/want weighting and adverse-consequence comparison.

How do I install Thinking Kepner Tregoe?

Run "npx skills add tjboudreaux/cc-thinking-skills --skill thinking-kepner-tregoe" 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 Kepner Tregoe work in Cursor and Codex?

Yes. Thinking Kepner Tregoe 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 Kepner Tregoe free?

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

Who made Thinking Kepner Tregoe?

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

Similar skills. From other creators.