Issue Tree Builder
Builds a MECE issue tree that breaks a business problem into clean, non-overlapping, fully-covering branches drilled deep enough to reach testable hypotheses. Use this skill whenever the user wants to decompose or break down a problem, asks "build me an issue tree", "is this MECE", "map out the possible causes", "what are all the drivers of X", or is staring at a big messy problem and needs structure. Trigger it for both diagnostic problems (why did something happen) and solution problems (how could we achieve a goal). Use it even when the user doesn't say "issue tree" — if they need to struct
Install
npx skills add AnugamChakra/think-like-a-strategy-consultant --skill issue-tree-buildergit clone --depth 1 https://github.com/AnugamChakra/think-like-a-strategy-consultant.git /tmp/think-like-a-strategy-consultant
mkdir -p ~/.claude/skills
cp -r /tmp/think-like-a-strategy-consultant/thinking-habit-skills/issue-tree-builder ~/.claude/skills/issue-tree-builderPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Issue Tree Builder
An issue tree is a map of a problem broken into parts that don't overlap and together miss nothing.
Think of how a navigation app splits a trip into legs: highway, city streets, final turn. Each leg
is distinct, together they cover the whole route, and if you skip one you get lost. MECE (mutually
exclusive, collectively exhaustive) is just the quality test you run on your own branches: no two
overlap, and nothing is missing.
The value of a tree is not that it looks tidy. It is that a good tree drills down until each bottom
branch becomes something you can actually go test. A one-level "tree" is useless.
## The method
**First, decide which kind of tree this is**, because it changes the whole structure. Infer it from
the question and say which you chose; only ask the user when it is genuinely ambiguous ("grow
revenue" could be either, "why did revenue fall" is not).
- A **diagnostic tree** works backward from a symptom to root causes ("why did revenue fall?" splits
into price, volume, mix, and so on).
- A **solution tree** works forward from a goal to the available options ("how could we grow share?"
splits into win new customers, grow existing, reduce churn, and so on).
Then build. Three rules make the tree worth anything:
1. **Drill at least three levels.** "Revenue is down" splitting into "price and volume" is a start,
not a tree. Push volume into new-customer volume and repeat-customer volume, then repeat-customerDetails
- Skill name
issue-tree-builder- Path
thinking-habit-skills/issue-tree-builder/SKILL.md- License
- MIT
- Repo updated
- 2 July 2026
FAQ
What does the Issue Tree Builder skill do?
Builds a MECE issue tree that breaks a business problem into clean, non-overlapping, fully-covering branches drilled deep enough to reach testable hypotheses. Use this skill whenever the user wants to decompose or break down a problem, asks "build me an issue tree", "is this MECE", "map out the possible causes", "what are all the drivers of X", or is staring at a big messy problem and needs structure. Trigger it for both diagnostic problems (why did something happen) and solution problems (how could we achieve a goal). Use it even when the user doesn't say "issue tree" — if they need to struct
How do I install the Issue Tree Builder skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add AnugamChakra/think-like-a-strategy-consultant --skill issue-tree-builder. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Issue Tree Builder popular?
It lives in AnugamChakra/think-like-a-strategy-consultant, which has 33 GitHub stars and 8 forks.
Related skills
3c Snapshot
33AnugamChakra/think-like-a-strategy-consultant
Runs a fast Company / Customer / Competitor scan of a business and forces the intersections to surface the real strategic opening. Use this skill whenever the user needs a quick situational read before a decision, says "give me a 3C", "size up this business", "what's our right to win", "who are we and who are we up against", or is writing background analysis that risks being three disconnected paragraphs. Trigger it whenever someone needs to understand a company's strategic position quickly, even if they don't name the 3Cs. Its whole value is the intersection, not the three descriptions.
Advantage Auditor
33AnugamChakra/think-like-a-strategy-consultant
Tests whether a company's strength is a real, defensible competitive advantage by running it through VRIO, then tiers it and gives a resource-allocation implication. Use this skill whenever the user claims or questions a competitive advantage, says "is this actually a moat", "what's our competitive advantage", "can competitors copy this", "run VRIO on our X", or is deciding where to invest to defend an edge. Trigger it whenever someone treats a strength as an advantage without testing it. The core lesson: every company has strengths, very few have advantages.
Daily Casing Drill
33AnugamChakra/think-like-a-strategy-consultant
Generates one everyday-life strategy case per session, invites the user's structured attempt, and grades it on framework, hypothesis, and "so what". Use this skill whenever the user wants to practice strategic thinking, says "give me a case", "daily drill", "let me practice", "quiz me on strategy", "help me build the muscle", or wants a repeatable reasoning workout. Trigger it whenever someone wants reps rather than an answer to a real work problem. It turns ordinary observations into practice that makes the strategic mindset reflexive.
Video Project Github
38vargHQ/skills
Keep an AI video project, or any agent-built project, in a private GitHub repo, even when the person has never used git. The agent does everything: creates the private repo, keeps keys out, saves a version after every approved step, stores big video and audio outside git so GitHub's 100 MB limit never hits, and restores the whole project byte for byte on a new laptop. Sets up the folder layout for mood boards, script, sound, characters, blockout, shots and the edit as text (HyperFrames, Remotion, ffmpeg), records the prompt, model, seed and cost of every take, and gives an undo for anything. U
Lfe Archivist
44StChiotis/Library-First-Engineering
Act as the Archivist for an LFE-compliant project. Use when a change is approved and needs documentation sync, changelog updates, or pipeline status cleanup.
Audit
57javimosch/supercli
Use this skill when the user wants to audit collaborators hooks and deploy keys on github repositories.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.