fan-out
Skill0 starsChanged 3 months agoMITView on GitHub
Delegate work to parallel subagents correctly — when to fan out, the briefing contract, and merge protocol. Use whenever a plan contains independent subtasks, broad multi-source searches, parallel verification, or the user says in parallel, agents, or delegate. Also read it to decide NOT to fan out.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- SylphxAI/skillstheir own version, first seen Nov 16, 2026
- Suge8/friedbuntheir own version, first seen Nov 8, 2026
- keli-wen/rondotheir own version, first seen Oct 25, 2026
- stjarnstrom/spec-systemtheir own version, first seen Oct 15, 2026
- keli-wen/dev-skillstheir own version, first seen Oct 13, 2026
- me2resh/apexyardtheir own version, first seen Oct 8, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- me2resh/apexyard★ 542same name
- Suge8/friedbun★ 13same name
- keli-wen/dev-skills★ 12same name
- keli-wen/rondo★ 12same name
- alexanderpino/skills★ 1same name
- SylphxAI/skills★ 1same name
- haliphax-ai/skills★ 0same name
- reaatech/mcp-gateway★ 0same name
- stjarnstrom/spec-system★ 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 repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brainstormSkill
- cleanupSkill
- context-managementSkill
- critiqueSkill
- debuggingSkill
- design-decisionsSkill
- diff-managementSkill
- final-checkSkill
- handoverSkill
- loopsSkill
- memorySkill
- orientSkill
- planningSkill
- researchSkill
- roadmapSkill
- verificationSkill
- web-testingSkill
- writing-reviewSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
5
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 16
When you'd spend more effort briefing than doing.
- Distinctive: line 21
Every spawned agent gets ALL of:
- Distinctive: line 35
Keep a fan-out ledger in the task list: one task per agent, marked with its scope.
- Distinctive: line 41
Verify each result against its brief BEFORE integrating — spot-check claims, run its outputs, read its diffs.
- Distinctive: line 42
Look for cross-agent conflicts: contradictory findings, incompatible edits, duplicated work.
“Common” is measured: kept by at least 6 in 10 of the 7 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
Agent fan-out
When to fan out
- Subtasks are independent (no shared files, no ordering dependency) AND each needs meaningful exploration or generation.
- Broad research/search across many sources or files where you only need conclusions.
- Independent verification: a fresh critic agent reviewing finished work.
When NOT to fan out
- Single lookups you can do in 1–2 tool calls yourself.
- Tightly coupled edits (agents stepping on each other's files).
- When you'd spend more effort briefing than doing.
- Deep sequential reasoning — parallelism doesn't help a chain.
Briefing an agent (the contract)
Every spawned agent gets ALL of:
- Scope — exactly what to do, with file paths / sources / boundaries.
- Deliverable — exact output format ("return a markdown list of findings, each with file:line evidence").
- Non-goals — what NOT to touch or do. Explicitly forbid writing outside its assigned paths.
- Context — the minimum background it needs (it starts with zero context; it cannot see this conversation).
- Quality bar — how it should verify its own work before reporting.
A brief the agent could misinterpret WILL be misinterpreted. Write briefs like API contracts.
Orchestration rules
- Launch independent agents in parallel — one message, multiple Task calls.
- Never let two agents write to the same file. Partition by directory or file list.
- Writers get disjoint scopes; readers can overlap freely.
- Keep a fan-out ledger in the task list: one task per agent, marked with its scope.
- Cap parallelism at what you can meaningfully verify (typically 3–5 agents per wave).
- For continuing work with an existing agent, message it rather than spawning a fresh one and re-briefing.
Merging results (fan-in)
- Verify each result against its brief BEFORE integrating — spot-check claims, run its outputs, read its diffs. Blind merging is a protocol violation.
- Look for cross-agent conflicts: contradictory findings, incompatible edits, duplicated work.
- Integrate sequentially, verifying after each merge, not after all merges.
- Record in the plan which results were accepted, rejected, or reworked — and why (design decision if significant).
Failure handling
An agent that returns garbage gets ONE re-brief with the misunderstanding corrected. If it fails again, do that subtask yourself — repeated re-delegation wastes more than it saves.
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.

