Babysitter dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
install
source · Clone the upstream repo
git clone https://github.com/a5c-ai/babysitter
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/a5c-ai/babysitter "$T" && mkdir -p ~/.claude/skills && cp -r "$T/library/methodologies/superpowers/skills/dispatching-parallel-agents" ~/.claude/skills/a5c-ai-babysitter-dispatching-parallel-agents && rm -rf "$T"
manifest:
library/methodologies/superpowers/skills/dispatching-parallel-agents/SKILL.mdsource content
Dispatching Parallel Agents
Overview
One agent per independent problem domain. Let them work concurrently.
Core principle: Dispatch one agent per independent problem domain.
When to Use
- 3+ test files failing with different root causes
- Multiple subsystems broken independently
- Each problem understood without context from others
- No shared state between investigations
When NOT to Use
- Failures are related (fix one might fix others)
- Need full system state understanding
- Agents would interfere (editing same files)
Process
- Identify independent domains
- Dispatch agents in parallel (ctx.parallel.all)
- Check for conflicts between solutions
- Run full test suite to verify integration
Agents Used
- Process agents defined in
dispatching-parallel-agents.js
Tool Use
Invoke via babysitter process:
methodologies/superpowers/dispatching-parallel-agents