NickolasBenakis/agent-playbook / skills/fanout
fanout
VerifiedHuman-in-the-loop workflow for high-impact, high-attention work. The main session stays with the human and delegates each discrete fix or feature to a subagent that returns a PR or verified diff. Use for core product work and dogfooding sessions.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.0 KB |
SKILL.md
View on GitHub---
name: fanout
description: Human-in-the-loop workflow for high-impact, high-attention work. The main session stays with the human and delegates each discrete fix or feature to a subagent that returns a PR or verified diff. Use for core product work and dogfooding sessions.
---
# Fanout
The human drives; you dispatch. The main session is a control room, not a
workbench: keep its context for decisions and coordination, and push execution
into subagents.
## How to run it
1. As the human dumps work ("this is broken", "add X", "make Y faster"), turn
each into a self-contained brief with the `delegate` skill, plus the
branch name `fanout/<short-slug>` and the finish line: tests/typecheck
pass, PR opened (or diff ready if no remote).
2. Launch one subagent per independent item, in an isolated worktree when the
tool supports it. Run several at once only when AGENTS.md rule 6 says
it's faster; otherwise one at a time, and a single small item can just be
done.
Items that touch the same files go to one subagent, sequentially.
3. Keep a running board in your replies, updated whenever it changes:
| Item | Agent | State | PR |
|------|-------|-------|----|
4. When a subagent returns, verify its claim before marking it done: check
the test output, and for non-trivial diffs run the `playbook-reviewer`
subagent with the item's acceptance criteria. If it failed, re-brief once
with what went wrong; on a second failure, bring it to the human.
5. Let the human keep going: "fix this with a subagent" should be all it takes.
Don't ask for confirmation on items that are clearly scoped.
## In bb
Child threads work as subagents and show up in the sidebar:
```sh
bb thread spawn --parent-self --new-environment worktree \
--title "[fanout] <task> — building" --prompt-file brief.md
bb thread wait <id> # or rely on parent notifications
```
## Done
Report the board, with every row either `pr-open`, `done`, or `needs-you: <why>`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |