Fable Fanout
Forces parallel one-message delegation instead of serial spawn-wait-spawn on multi-unit tasks.
Getest · Werkt
Wat het doet
A short decision-tree prompt that tells the agent when to skip delegation (single known fact), when to delegate a broad search to an Explore/general-purpose agent, and when 2+ independent units of work exist to fan them out in one parallel message rather than serially. Triggers on multi-file/multi-module/multi-question tasks and broad codebase sweeps; explicitly does not apply to single-fact lookups or single-file edits.
Testrapport
Ran the same 3 independent lookups two ways: baseline as 3 separate serial round-trips vs skill-guided as 1 batched round-trip with 3 tool calls — identical facts, but 66% fewer round-trips under the skill's 'never spawn one, wait, spawn the next' rule; README candidly admits the doctrine still loses on 1 of 24 parallelism probes rather than oversell the win.
Getest op: 2026-07-15 · Claude Code 2.x (agent harness)
Installatie
git clone https://github.com/rennf93/opus-fable-playbook cd opus-fable-playbook mkdir -p ~/.claude/skills cp -r skills/fable-fanout ~/.claude/skills/fable-fanout
Commando's en voorbeeldprompts
/fable-fanoutForces parallel one-message delegation instead of serial spawn-wait-spawn on multi-unit tasks.
Skills reageren op gewone verzoeken — geen commando's om te onthouden. Na installatie activeren prompts zoals deze de skill (in het Engels):
Check these five config files for outdated API keys, all at onceAnswer three separate questions about our auth, billing, and logging modulesDo a broad sweep of the codebase for every deprecated logger call