issue-tree-builder

issue-tree-builder is a skill for Claude Code, Codex from sruthir28/enterprise-ai-skills. It costs 62 tokens per session (1,749 once invoked), scanned A, original, MIT.

A structured tree for breaking a difficult question into smaller questions that do not overlap and together cover the problem. It is a consulting method for planning analysis and deciding what to investigate.

In plain words
What is it for?
Use it to structure strategy questions, analysis plans, workstreams, and case-interview problems.
Why use it?
It prevents important parts of a problem from being missed and turns a broad question into focused work areas and testable ideas.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to structure strategy questions, analysis plans, workstreams, and case-interview problems.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sruthir28/enterprise-ai-skills/issue-tree-builder
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add sruthir28/enterprise-ai-skills --skill issue-tree-builder
Clone the repo
git clone --depth 1 https://github.com/sruthir28/enterprise-ai-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for issue-tree-builder

README.md
[![agentmods](https://agentmods.dev/badge/skills/sruthir28/enterprise-ai-skills/issue-tree-builder/github.svg)](https://agentmods.dev/skills/sruthir28/enterprise-ai-skills/issue-tree-builder)
Your own site
<a href="https://agentmods.dev/skills/sruthir28/enterprise-ai-skills/issue-tree-builder"><img src="https://agentmods.dev/badge/skills/sruthir28/enterprise-ai-skills/issue-tree-builder/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for issue-tree-builder

Your own site · 80×15
<a href="https://agentmods.dev/skills/sruthir28/enterprise-ai-skills/issue-tree-builder"><img src="https://agentmods.dev/badge/skills/sruthir28/enterprise-ai-skills/issue-tree-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,749 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.01749
Opus 5 $0.00031 $0.00874
Sonnet 5 $0.00012 $0.00350
Haiku 4.5 $0.00006 $0.00175

Measured 11d ago against content hash 780098f7ad7b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

issue-tree-builder scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

issue-tree-builder/SKILL.md · 184 lines

How it starts

The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Issue Tree Builder

A structured approach to breaking down complex problems into actionable components using MECE principles.

What is an Issue Tree?

A visual hierarchy that decomposes a governing question into increasingly specific sub-questions or components. Used in consulting to structure analysis, prioritize workstreams, and develop hypotheses before solutioning.

Key characteristics:

  • Top-down structure (question → branches → sub-branches)
  • MECE at each level (branches don't overlap, collectively cover the problem)
  • Hypothesis-driven (based on initial beliefs about what matters)
  • Actionable at terminal branches (lowest level = things you can analyze or do)

Framework Components

Level 0: Governing Question

  • The main strategic question to answer
  • Must be specific and answerable
  • Examples: "How to grow revenue 40% in 12 months?", "Should we enter the European market?"

Level 1-2: Major Branches (typically 3 branches)

  • Consulting "rule of 3" - aim for three major dimensions
  • Decompose to fundamentals first, not actions
  • Must be MECE
  • Often structured around fundamental problem drivers:
    • Revenue problems: Price × Quantity × Pipeline/funnel
    • Profit problems: Revenue - Cost
    • Growth problems: New customers, Expand existing, New products
    • Market entry: Market attractiveness, Competitive position, Capability to win

Level 2: Sub-branches

  • One more level of decomposition from major branches
  • 2 levels total from governing question
  • Terminal branches should be clear hypotheses to test with data
  • Keep simple and focused

Core Principles

MECE (Mutually Exclusive, Collectively Exhaustive)

  • No overlap between branches at same level
  • Together they cover all relevant aspects
  • Test: Can you classify any answer element into exactly one branch?

Hypothesis-Driven with Data

  • Start with beliefs about what matters most
  • Structure tree to test key hypotheses
  • Each terminal branch = hypothesis to prove/disprove with data
  • Back findings with analysis
  • Example: "Hypothesis: Pricing 20% below market drives volume" → Test with data

Read the full file on GitHub · 184 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 184 lines · 62 tokens per session scan A 780098f7ad7b

Subscribe to this mod's changes

issue-tree-builder is a skill published in the GitHub repository sruthir28/enterprise-ai-skills (138 stars, last pushed 9d ago), licensed MIT. It adds 62 tokens to every session and 1,749 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.