issue-tree
Skill1 starsChanged 22 days agoMITView on GitHub
Structures an ambiguous business problem into a MECE issue tree when the team needs a rigorous path to an answer.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- fzfclee/consulting-skillstheir own version, first seen Oct 13, 2026
- imran-sayed-pro/claude-skillstheir own version, first seen Jul 11, 2026
- CAPP-Financials/Consulting_Braintheir own version, first seen Apr 24, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- fzfclee/consulting-skills★ 6same name
- CAPP-Financials/Consulting_Brain★ 0same name
- imran-sayed-pro/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository133 other files it gives its agents.
- templates/CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- access-control-auditSkill
- ai-opportunity-scanSkill
- ai-policy-writerSkill
- annual-budget-builderSkill
- application-portfolio-mapSkill
- architecture-fit-checkSkill
- automation-backlogSkill
- benefits-realisationSkill
- board-paperSkill
- bottleneck-removalSkill
- break-even-modelSkill
- budget-variance-analystSkill
- business-continuity-plannerSkill
- business-valuationSkill
- capacity-planningSkill
- case-study-writerSkill
- cash-flow-forecastSkill
- change-adoptionSkill
- change-impactSkill
- channel-profitabilitySkill
- churn-cohort-analysisSkill
- client-handoverSkill
- client-kickoffSkill
- client-profitabilitySkill
- client-relationship-managerSkill
- closeout-packSkill
- compensation-bandsSkill
- competitor-mapperSkill
- contribution-marginSkill
- cost-structure-analystSkill
- crisis-communicationsSkill
- customer-insight-synthesiserSkill
- customer-interview-designerSkill
- customer-journey-mapSkill
- customer-segmenterSkill
- cyber-risk-assessmentSkill
- dashboard-requirements-plannerSkill
- data-lineage-mapperSkill
- data-quality-auditSkill
- decision-logSkill
- decision-memoSkill
- decision-rightsSkill
- delivery-model-selectorSkill
- demand-validatorSkill
- discount-governanceSkill
- discovery-call-facilitationSkill
- discovery-call-prepSkill
- discovery-question-designSkill
- discovery-synthesisSkill
- engagement-outcomesSkill
- evidence-synthesiserSkill
- executive-dashboardSkill
- executive-summarySkill
- fee-settingSkill
- financial-statement-diagnosticSkill
- fundraising-readinessSkill
- funnel-diagnosticSkill
- go-to-marketSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use before research or analysis when the central question is unclear, too broad or disputed.
- Distinctive: line 29
Every branch directly helps answer the central question
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Issue Tree
When to use it
Use before research or analysis when the central question is unclear, too broad or disputed.
What Claude needs
- The decision or problem statement
- Relevant background from client-context.md
- Known constraints, definitions and time horizon
- Existing evidence or stakeholder views
Method
- Rewrite the problem as one decision-focused question with a clear boundary.
- Choose a logic type: diagnostic, solution, profitability or process.
- Build two to four mutually exclusive, collectively exhaustive first-level branches.
- Decompose each branch into testable sub-questions without mixing causes and solutions.
- Mark dependencies, missing evidence and branches with the greatest decision impact.
- Stress-test the tree for overlap, omissions and answerability.
Output format
Provide the problem statement, an indented issue tree, a branch rationale table and the next analyses in priority order.
Quality checks
- Every branch directly helps answer the central question
- Sibling branches do not overlap materially
- Leaf questions can be answered with identifiable evidence
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.