/subagent-fanout

Parallelize independent sub-jobs across fresh-context subagents instead of one bloated context. Use when a goal branches into many independent pieces.

BOOST

archive228@archive228

GitHub

From plugin

loopkit

75553 skills1 agent4 commands2 MCP

Install

$ npx -y skills add Archive228/loopkit --skill subagent-fanout --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/subagent-fanout

Context preview

The summary Claude sees to decide when to auto-load this skill.

Parallelize independent sub-jobs across fresh-context subagents instead of one bloated context. Use when a goal branches into many independent pieces.

SKILL.md

subagent-fanout.SKILL.md

name: subagent-fanout
description: Parallelize independent sub-jobs across fresh-context subagents instead of one bloated context. Use when a goal branches into many independent pieces.
when_to_use: analyze N items, fix M files, search K sources, anything embarrassingly parallel

Subagent Fan-out

One context loaded with ten jobs' worth of material is the exact shape that triggers context rot. Ten small contexts don't.

Spawn one subagent per independent unit (one file, one source, one check). Each gets a fresh context window.
An **orchestrator** synthesizes their results — it never does the per-unit work itself.
Give each worker a tight role and only the input it needs.
Use ONLY when the pieces are genuinely independent. Sequential dependencies stay in one chain.

Fan-out for breadth (research, multi-file edits, multi-source verification). Keep it serial when step N needs step N-1's output.

Read it on GitHub ↗

Ships withloopkit

33 battle-tested skills + minimal .claude harness for any coding agent (Claude Code, Cursor, Codex, Gemini CLI).

Get the whole plugin

Stats

Node Bash SQL Git GitHub

+4 tags

Markdown Anthropic Gemini MCP

755

Stars

124