spawn — Claude Code skill: what it does, how to install
Runs parallel subagents in isolated git worktrees to compete on a session task. Helpful when you want multiple implementation strategies tested at once.
/plugin marketplace add alirezarezvani/claude-skills
/plugin install agenthub@claude-code-skillsWhat spawn does
The skill loads session settings from .agenthub/sessions/{session-id}/config.yaml and prepares assignments in .agenthub/board/dispatch/. It then launches all subagents simultaneously in a single message using Claude Code's Agent tool with isolation: "worktree". Each subagent works inside its own worktree, commits progress, and writes final notes to .agenthub/board/results/.
Four dispatch templates are supported: optimizer, refactorer, test-writer, and bug-fixer. Each template enforces a specific workflow, such as test coverage loops or repeated latency benchmarks. After launch, the session state switches to running via session_manager.py.
Use this skill when tackling complex refactoring or elusive bugs with alternative approaches. Running isolated worktrees for straightforward single-file edits is unnecessary overhead.
What it helps with
- run parallel subagents on a single task across isolated git worktrees
- dispatch competing optimization or refactoring strategies via templates
- prevent agents from overwriting shared code during concurrent exploration
- aggregate structured agent summaries into markdown result boards
Example prompts for the agent
- /hub:spawn
- /hub:spawn --template refactorer
- /hub:spawn 20260317-143022 --template optimizer
How to install spawn
1Plugin marketplace
/plugin marketplace add alirezarezvani/claude-skills/plugin install agenthub@claude-code-skillsThis installs the whole agenthub plugin with all its skills
2Skills CLI (Vercel)
npx skills add alirezarezvani/claude-skills --skill spawn -a claude-code3Manually: put the files in place
~/.claude/skills/spawn/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/spawn/
Manually: put the files in place
.agents/skills/spawn/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/spawn/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install alirezarezvani/claude-skills spawn2Manually: put the files in place
.github/skills/spawn/SKILL.mdPlatform CLI
gemini skills install https://github.com/alirezarezvani/claude-skills --path engineering/agenthub/skills/spawnManually: put the files in place
.devin/skills/spawn/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set349
The whole set →Similar
Questions about spawn
How to install spawn in Claude Code?
Run npx skills add alirezarezvani/claude-skills --skill spawn -a claude-code or save the definition file to ~/.claude/skills/spawn/SKILL.md.
What does the spawn skill do?
It spins up N parallel subagents in isolated git worktrees so they can independently test different solutions for an active AgentHub session.
Which templates are supported by /hub:spawn?
The skill includes optimizer, refactorer, test-writer, and bug-fixer templates, assigning distinct problem-solving strategies to each agent.
Source text
SKILL.md · MIT
---
name: "spawn"
description: "Launch N parallel subagents in isolated git worktrees to compete on the session task. Use when the user runs /hub:spawn or asks to start the competing agents for an initialized AgentHub session."
metadata:
command: /hub:spawn
---
# /hub:spawn — Launch Parallel Agents
Spawn N subagents that work on the same task in parallel, each in an isolated git worktree.
## Usage
```
/hub:spawn # Spawn agents for the latest session
/hub:spawn 20260317-143022 # Spawn agents for a specific session
/hub:spawn --template optimizer # Use optimizer template for dispatch prompts
/hub:spawn --template refactorer # Use refactorer template
```
## Templates
When `--template <name>` is provided, use the dispatch prompt from `../agenthub/references/agent-templates.md` instead of the default prompt below. Available templates:
| Template | Pattern | Use Case |
|----------|---------|----------|
| `optimizer` | Edit → eval → keep/discard → repeat x10 | Performance, latency, size reduction |
| `refactorer` | Restructure → test → iterate until green | Code quality, tech debt |
| `test-writer` | Write tests → measure coverage → repeat | Test coverage gaps |
| `bug-fixer` | Reproduce → diagnose → fix → verify | Bug fix with competing approaches |
When using a template, replace all `{variables}` with values from the session config. Assign each agent a **different strategy** appropriate to the template and task — diverse strategies maximize the value of parallel exploration.
## What It Does
1. Load session config from `.agenthub/sessions/{session-id}/config.yaml`
2. For each agent 1..N:
- Write task assignment to `.agenthub/board/dispatch/`
- Build agent prompt with task, constraints, and board write instructions
3. Launch ALL agents in a **single message** with multiple Agent tool calls:
```
Agent(
prompt: "You are agent-{i} in hub session {session-id}.
Your task: {task}
Read your full assignment at .agenthub/board/dispatch/{seq}-agent-{i}.md
Instructions:
1. Work in your worktree — make changes, run tests, iterate
2. Commit all changes with descriptive messages
3. Write your result summary to .agenthub/board/results/agent-{i}-result.md
Include: approach taken, files changed, metric if available, confidence level
4. Exit when done
Constraints:
- Do NOT read or modify other agents' work
- Do NOT access .agenthub/board/results/ for other agents
- Commit early and often with descriptive messages
- If you hit a dead end, commit what you have and explain in your result",
isolation: "worktree"
)
```
4. Update session state to `running` via:
```bash
python {skill_path}/scripts/session_manager.py --update {session-id} --state running
```
## Critical Rules
- **All agents in ONE message** — spawn all Agent tool calls simultaneously for true parallelism
- **isolation: "worktree"** is mandatory — each agent needs its own filesystem
- **Never modify session config** after spawn — agents rely on stable configuration
- **Each agent gets a unique board post** — dispatch posts are numbered sequentially
## After Spawn
Tell the user:
- {N} agents launched in parallel
- Each working in an isolated worktree
- Monitor with `/hub:hub-status`
- Evaluate when done with `/hub:eval`
© Alireza Rezvani · MIT · alirezarezvani/claude-skills