fractal-delegation
Skill0 starsChanged 28 days agoMITView on GitHub
Every task with 2+ independent workstreams, or any task that would take >15 minutes as solo work. Also triggered by chairman voice dumps with multiple requirements. For EVERY task, answer these questions: Launch 3-5 sub-agents in background for research while you implement. When: Need information, not code changes. Protects your context window. Each agent works in an isolated git worktree. Changes merge back. When: Code changes in non-overlapping files. For large features spanning multiple packages. When: Features spanning 3+ packages…
- Reads credentials
4 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- naman10parikh/pennyword for word, first seen Nov 8, 2026
- naman10parikh/wikimemedited, first seen Nov 8, 2026
- naman10parikh/turboword for word, first seen Oct 25, 2026
- naman10parikh/agentgridedited, first seen Oct 20, 2026
Other versions4 projects use a version of this.
Word for word · 2
- naman10parikh/penny★ 0100% same
- naman10parikh/turbo★ 0100% same
Edited · 2
- naman10parikh/agentgrid★ 996% same
- naman10parikh/wikimem★ 893% same
Wrote their own version · 0
None found.
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 repository59 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- agent-runtimeSkill
- frontend-designSkill
- architectSkill
- deep-thinkSkill
- design-systemsSkill
- ecosystem-referenceSkill
- harness-reviewSkill
- heartbeatSkill
- integrate-resourcesSkill
- llm-council-critiqueSkill
- loop-createSkill
- mcp-setupSkill
- memory-compressionSkill
- memorySkill
- model-routingSkill
- oss-project-scaffoldSkill
- playwright-cliSkill
- repo-scoutSkill
- self-improveSkill
- skill-creatorSkill
- skill-routingSkill
- sprintSkill
- test-visualSkill
- troubleshootSkill
- ux-auditSkill
- Accessibility AuditorSkill
- artifacts-builderSkill
- brand-guidelinesSkill
- canvas-designSkill
- frontend-patternsSkill
- design-mirrorSkill
- design-system-starterSkill
- design-to-codeSkill
- feature-design-assistantSkill
- figma-implement-designSkill
- frontend-designSkill
- frontend-dev-guidelinesSkill
- mobile-designSkill
- motion-canvasSkill
- pixel-agent-uiSkill
- pixel-animateSkill
- pixel-anti-slopSkill
- pixel-brain-pageSkill
- pixel-migrate-next16Skill
- pixel-rsc-boundarySkill
- pixel-ship-gateSkill
- premium-web-designSkill
- senior-frontendSkill
- shadcnSkill
- tailwind-design-systemSkill
- tailwind-patternsSkill
- theme-factorySkill
- ui-design-systemSkill
- ui-ux-pro-maxSkill
- ux-researcher-designerSkill
- web-design-guidelinesSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 14 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈14
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 5
Every task with 2+ independent workstreams, or any task that would take >15 minutes as solo work.
- Distinctive: line 136
When done: signals PARENT's signal dir
- Distinctive: line 145
Decision: Use Pattern E when you'd naturally say "this VP is really a CEO of its own team."
- Very specific: line 163
All terminals share tasks via CLAUDE_CODE_TASK_LIST_ID=energy-main.
- Distinctive: line 165
Use TaskCreate/TaskUpdate across terminals
- Distinctive: line 167
Check TaskList before starting work — another terminal may have claimed it
- Distinctive: line 174
VP mediate: If worker fails, the team lead reviews and redirects
- Distinctive: line 175
CEO escalate: If VP can't resolve, CEO takes over (or escalates to chairman)
- Distinctive: line 188
Don't delegate then do the same work yourself (duplicate effort)
- Distinctive: line 189
Don't use worktrees for read-only research (unnecessary overhead)
- Distinctive: line 190
Don't spawn agents for tasks that take <2 minutes solo
- Distinctive: line 191
Don't create teams of 1 (that's just a sub-agent)
- Distinctive: line 192
Don't delegate architecture decisions — make them yourself, delegate implementation
- Distinctive: line 193
Don't let agents run unmonitored >30 min — check progress via TaskList
- Distinctive: line 194
Don't skip the research phase — always gather context before implementation
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: Fractal Delegation (The CEO Operating System)
Trigger
Every task with 2+ independent workstreams, or any task that would take >15 minutes as solo work. Also triggered by chairman voice dumps with multiple requirements.
The Organizational Hierarchy
CHAIRMAN (Naman) — Vision, capital, objective function
│
CEO (You — Opus) — Decompose, route, delegate, monitor, integrate
│
├── VP Research (Agent Team / Sub-agents)
├── VP Frontend (Agent Team with worktree)
├── VP Backend (Agent Team with worktree)
└── VP Quality (Sub-agents for review/test)
│
└── Workers (Sub-agents within each VP)
- Research workers (Haiku)
- Code workers (Sonnet)
- Review workers (Sonnet)The Decision Matrix
For EVERY task, answer these questions:
1. Can work be parallelized?
- NO → Do it yourself (sequential dependency)
- YES → Continue to #2
2. Does it modify code files?
- NO (research, reading, analysis) → Sub-agents (parallel, no isolation needed)
- YES → Continue to #3
3. Do the code changes overlap (same files)?
- YES → Sub-agents for research, YOU implement (avoid merge conflicts)
- NO (different files/packages) → Agent Teams with worktree isolation
4. Is this a complex multi-domain task?
- YES → Full swarm: Agent Teams + sub-agents within each team (Pattern D)
- NO → Single agent with worktree (Pattern B)
Delegation Patterns
Pattern A: Research Swarm (most common)
Launch 3-5 sub-agents in background for research while you implement.
Agent(research-1, background, haiku) → "Find all instances of X in codebase"
Agent(research-2, background, haiku) → "Read competitor docs for pattern Y"
Agent(research-3, background, haiku) → "Check if library Z supports feature W"
YOU → Start implementing based on what you already knowWhen: Need information, not code changes. Protects your context window.
Pattern B: Worktree Agents (for multi-file features)
Each agent works in an isolated git worktree. Changes merge back.
Agent(frontend, worktree, sonnet) → "Build UI component in packages/web/"
Agent(backend, worktree, sonnet) → "Build API route in packages/web/src/app/api/"
Agent(tests, worktree, sonnet) → "Write tests for the feature"
YOU → Orchestrate, review, merge, resolve conflictsWhen: Code changes in non-overlapping files.
Pattern C: Fractal (agents containing sub-agents)
For large features spanning multiple packages.
Agent(infra-team, worktree, sonnet) → {
This agent internally spawns sub-agents for:
- Database schema design (haiku)
- API route scaffolding (sonnet)
- Type definitions (haiku)
}
Agent(ui-team, worktree, sonnet) → {
This agent internally spawns sub-agents for:
- Component research (haiku)
- Component implementation (sonnet)
- Visual test (sonnet)
}
YOU → Architecture decisions, final integration, production deployWhen: Features spanning 3+ packages or requiring 5+ agents.
Pattern D: Chairman Directive Swarm (for voice dumps)
Full decomposition of a complex chairman directive.
1. CEO parses directive → extracts EVERY requirement
2. CEO creates TaskList with all tasks + dependencies
3. For each independent workstream:
a. Launch background research agent (haiku) for context gathering
b. Wait for research results
c. Launch implementation agent (worktree, sonnet) with research context
4. CEO monitors via TaskList, integrates results
5. CEO commits stable checkpoint, updates handoffWhen: Chairman sends a multi-requirement voice dump.
Pattern E: Grid-Based Recursion (CEO-of-CEOs)
Physical tmux grid nesting. A VP spawns its own agent grid in a separate window, becoming a sub-CEO with its own workers. Enables unlimited parallel compute.
Root CEO (depth 0) → agentgrid 2x3 in window "company"
├── VP-Mercury (SUB_CEO=true) → creates window "company-mercury"
│ └── agentgrid 1x3: Trader, Analyst, Risk
├── VP-Saturn (SUB_CEO=true) → creates window "company-saturn"
│ └── agentgrid 2x2: Designer, Developer, Marketer, QA
├── VP-Dashboard (flat worker, no sub-grid)
└── ANVIL-QA (flat worker, waits for all sub-CEOs)Each sub-CEO:
- Reads mission brief (includes
CEO_DEPTH,COMPANY_ID,PARENT_COMPANY_ID) - Creates its own tmux window + agentgrid
- Writes sub-missions, injects into its workers
- Monitors via CronCreate on its own signal dir
- When done: signals PARENT's signal dir
When:
- 10+ tasks across multiple domains
- Each domain needs its own research → build → test cycle
- Chairman says "recursive", "CEO of CEOs", or "sub-grids"
- Overnight runs where maximizing parallelism matters
Decision: Use Pattern E when you'd naturally say "this VP is really a CEO of its own team."
See .claude/rules/recursive-grid.md for the full protocol.
Model Routing Per Role
| Role | Model | Cost/MTok | Why |
| CEO (orchestrator) | Opus | $15/$75 | Delegation decisions need deep reasoning |
| VP / Team lead | Sonnet | $3/$15 | Multi-file code changes, integration |
| Research worker | Haiku | $0.80/$4 | Fast, cheap — just reading/searching |
| Code worker | Sonnet | $3/$15 | Balanced speed + quality |
| Review worker | Sonnet | $3/$15 | Code review, security scan |
| Architecture worker | Opus | $15/$75 | Design trade-offs, deep analysis |
| Tier 0 (no model) | — | $0 | Formatting, linting, git ops, tests |
Cross-Terminal Coordination
All terminals share tasks via CLAUDE_CODE_TASK_LIST_ID=energy-main.
- Use TaskCreate/TaskUpdate across terminals
- Tasks tagged with terminal context (earning, content, spark, platform)
- Check TaskList before starting work — another terminal may have claimed it
Escalation Protocol (3-Tier)
Borrowed from Agent Orchestrator (Composio):
- Worker self-heal: Agent retries on failure up to 3x with different approaches
- VP mediate: If worker fails, the team lead reviews and redirects
- CEO escalate: If VP can't resolve, CEO takes over (or escalates to chairman)
When NOT to Delegate
- Single-file edits < 20 lines
- Bug fixes where you already know the cause
- Configuration changes (.env, package.json)
- Commits, deploys, git operations
- Anything requiring YOUR conversation context (user preferences, prior decisions)
- Architecture decisions — make them yourself, delegate implementation
Anti-Patterns
- Don't delegate then do the same work yourself (duplicate effort)
- Don't use worktrees for read-only research (unnecessary overhead)
- Don't spawn agents for tasks that take <2 minutes solo
- Don't create teams of 1 (that's just a sub-agent)
- Don't delegate architecture decisions — make them yourself, delegate implementation
- Don't let agents run unmonitored >30 min — check progress via TaskList
- Don't skip the research phase — always gather context before implementation
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.

