tiling-tree
/tiling-tree
Exhaustive problem space exploration using the MIT Synthetic Neurobiology "tiling tree" method. Partitions a problem into MECE (Mutually Exclusive, Collectively Exhaustive) subsets recursively via parallel subagents, then evaluates leaf ideas against specified criteria. Use when users say "tiling tree", "tile the solution space", "exhaustively explore approaches to", "what are all the ways to", or request a MECE breakdown of a problem. Requires orchestrating-chat-agents skill.
- Author
- oaustegard ↗
- Repository
- claude-skills ↗
- Licence
- MIT
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/tiling_tree.py
What it does and when to use it
Exhaustive problem space exploration using the MIT Synthetic Neurobiology "tiling tree" method. Partitions a problem into MECE (Mutually Exclusive, Collectively Exhaustive) subsets recursively via parallel subagents, then evaluates leaf ideas against specified criteria. Use when users say "tiling tree", "tile the solution space", "exhaustively explore approaches to", "what are all the ways to", or request a MECE breakdown of a problem. Requires orchestrating-chat-agents skill.
Triggers from the description
Original author description
Exhaustive problem space exploration using the MIT Synthetic Neurobiology "tiling tree" method. Partitions a problem into MECE (Mutually Exclusive, Collectively Exhaustive) subsets recursively via parallel subagents, then evaluates leaf ideas against specified criteria. Use when users say "tiling tree", "tile the solution space", "exhaustively explore approaches to", "what are all the ways to", or request a MECE breakdown of a problem. Requires orchestrating-chat-agents skill.
How it works
- Core Concept
- When to Use
- Setup
- Running the Tiling Tree
- Parameters
- Architecture
- Output
- Interpreting Results
SKILL.md preview
---
name: tiling-tree
description: Exhaustive problem space exploration using the MIT Synthetic Neurobiology "tiling tree" method. Partitions a problem into MECE (Mutually Exclusive, Collectively Exhaustive) subsets recursively via parallel subagents, then evaluates leaf ideas against specified criteria. Use when users say "tiling tree", "tile the solution space", "exhaustively explore approaches to", "what are all the ways to", or request a MECE breakdown of a problem. Requires orchestrating-chat-agents skill.
metadata:
version: 1.1.1
depends_on: orchestrating-chat-agents
---
# Tiling Tree
Implements the MIT Synthetic Neurobiology tiling tree method: recursively partition a problem space into non-overlapping, collectively exhaustive subsets until reaching actionable leaf ideas, then evaluate those leaves.
## Core Concept
The method's power comes from MECE splits forcing exploration of unfamiliar territory. A split is only valid when you can state precisely what each branch **excludes** — if you can't, the criterion is too vague and branches will overlap.
Key insight from the source method: always look for the "third option" that falls outside an obvious binary split. The bloodstream-secretion approach to neural recording only emerged because "wired vs. wireless" was defined precisely enough to reveal it covered neither case.
## When to Use
- "What are all the ways we could solve X?"
- "Apply the tiling tree method to Y"
- "Exhaustively map the solution space for Z"
- Any request for MECE decomposition of a problem domain
## Setup
Requires `orchestrating-chat-agents` skill to be installed. Load it first:
```python
import sys
sys.path.insert(0, '/mnt/skills/user/orchestrating-chat-agents/scripts')
from claude_client import invoke_claude, invoke_parallel, parse_json_response
```
## Running the Tiling Tree
```bash
# Basic usage
python3 /mnt/skills/user/tiling-tree/scripts/tiling_tree.py "Your problem here"
# With options
python3 /mnt/skills/user/tiling-tree/scripts/tiling_tree.py \
"How can we record neural activity?" \
--depth 3 \
--criteria "impact,novelty,feasibility" \
--output /mnt/user-data/outputs/neural_recording_tree.md
```
## Parameters
| Parameter | Default | Notes |
|-----------|---------|-------|
| `problem` | required | Natural language problem statement |
| `--depth` | 2 | Max recursion depth. Depth 2 ≈ 16 leaves, depth 3 ≈ 64 leaves |
| `--criteria` | `impact,novelty,feasibility` | Comma-separated evaluation dimensions |
| `--output` | `tiling_tree.md` | Output markdown path |
**Depth guidance:** Start with depth 2 to validate the problem framing. Increase to 3 only when the domain genuinely warrants it — depth 3 generates ~64 leaves and ~40 API calls.
## Architecture
- **Orchestrator** (this script): builds tree skeleton, dispatches parallel split jobs per level, merges results, detects gaps
- **Branch agents** (`invoke_parallel`): each receives one node to split, returns MECE branches with explicit exclusion statements
- **Evaluator** (`invoke_claude`): single agent scores all leaves for cross-leaf consistency
Parallel splitting happens level-by-level (not node-by-node), so a depth-2 tree makes only 2 API round-trips for the splitting phase regardless of branching factor.
## Output
A markdown file containing:
1. Full tree diagram with split criteria and evaluation scores at leaves
2. Ranked leaf table sorted by overall score
## Interpreting Results
Good trees have:
- Split criteria that are definitions, not questions ("energy source type" not "is it renewable?")
- Leaf exclusions that confirm non-overlap
- A "surprising" branch — something you wouldn't have thought of without the tree
If all leaves feel obvious, the split criteria were too coarse. Redo the tree with more precise definitions at the branch level where it went flat.
Files in this package (3)
- CHANGELOG.md 1 KB
- SKILL.md 4 KB
- scripts/tiling_tree.py 11 KB
Versions
The database has no other skills named tiling-tree.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version dc908e253867 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100mece-analysis
Structure thinking using Mutually Exclusive, Collectively Exhaustive categories. Use when breaking down problems or ensuring complete coverage. - 100issue-tree-builder
McKinsey-style issue tree framework for breaking down complex problems into MECE (Mutually Exclusive, Collectively Exhaustive) components. Use when users need to decompose strategic questions, structure analysis, create work plans, or prepare for case interviews. Apply… - 100mece-framework
Use when a problem, issue tree, option set, segmentation, workplan, hypothesis set, risk list, or recommendation structure must be mutually exclusive and collectively exhaustive. Use when applying MECE, no-overlap/no-gap structuring, consulting issue decomposition, taxonomy… - 100structured-problem-solving
The structured problem solving method used in strategy work, applied to any messy business question. Produces a closed problem statement, a mutually exclusive and collectively exhaustive tree, a day-one hypothesis written to be attacked, a workplan where every analysis is one… - 100mece
Activate when: user says 'decompose this', 'structure this thinking', 'MECE', 'issue tree', 'Minto Pyramid', 'how do we cover all the cases without double-counting', a problem feels too big to think about cleanly, a list of options is messy or overlapping, an analysis keeps… - 100issue-trees
Use issue trees to break complex problems into mutually exclusive and collectively exhaustive branches. Use when structuring problem solving, root cause analysis, solution exploration, or consulting-style decomposition.