
Spawn
Run competing agent implementations in parallel git worktrees on the same session task to pick the best diff faster.
Overview
Spawn is an agent skill most often used in Build (also Ship) that launches parallel subagents in isolated git worktrees to compete on the same session task.
Install
npx skills add https://github.com/alirezarezvani/claude-skills --skill spawnWhat is this skill?
- Launches N parallel subagents, each in an isolated git worktree on the same session task
- Session targeting via latest session ID or explicit timestamp (e.g. `20260317-143022`)
- Four dispatch templates: optimizer, refactorer, test-writer, and bug-fixer with distinct iterate patterns
- Template table defines optimizer (edit→eval×10), refactorer (restructure→green tests), test-writer (coverage loop), bug-
- `--template` swaps dispatch prompts from `references/agent-templates.md` and assigns diverse per-agent strategies
- 4 named dispatch templates: optimizer, refactorer, test-writer, bug-fixer
- Optimizer pattern: edit → eval → keep/discard → repeat ×10
Adoption & trust: 1.4k installs on skills.sh; 17.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are stuck on a hard coding task and a single agent thread wastes time on one approach while git state gets messy.
Who is it for?
Claude Code hub users who already run session-based workflows and want parallel exploration on performance, refactors, tests, or bugs.
Skip if: Repos without git worktree discipline, non-coding tasks, or builders who only need a single linear agent edit with no merge comparison.
When should I use this skill?
Launch N parallel subagents in isolated git worktrees to compete on the session task via `/hub:spawn` or `--template` modes.
What do I get? / Deliverables
You get N isolated worktree branches with template-driven competing implementations so you can merge or cherry-pick the winning approach and continue the hub session.
- N parallel git worktree branches with agent-produced changes for the same task
- Template-filled dispatch prompts per agent strategy from agent-templates.md
- Comparable implementation sets for merge, cherry-pick, or discard
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Parallel subagent dispatch is core build-phase agent tooling—where solo builders wire Claude/Cursor workflows into the repo, not where they market the product. Isolated worktrees plus `/hub:spawn` session orchestration is explicitly agent-tooling: multiplying agent capacity on one codebase task.
Where it fits
Spawn four refactorer agents with different structural strategies on the same hub session before picking a merge candidate.
Race optimizer agents on API latency reduction with edit-eval loops in separate worktrees.
Deploy test-writer templates in parallel to close coverage gaps ahead of release.
Use bug-fixer templates so multiple agents reproduce and fix the same defect for comparison in PR review.
How it compares
Orchestration workflow for parallel agent runs—not a single-shot code generator or an MCP server integration.
Common Questions / FAQ
Who is spawn for?
Solo and indie builders using Claude Code hub sessions who want multiple agents to tackle the same task in separate worktrees and compare outcomes.
When should I use spawn?
During build for agent-tooling-heavy implementation; in ship when running parallel fix or test-coverage strategies before review; when optimizer/refactorer templates match latency or debt goals.
Is spawn safe to install?
It drives parallel git worktrees and agent edits—expect broad filesystem and git effects; confirm scope in SKILL.md and review Security Audits on this Prism page before running on production branches.
SKILL.md
READMESKILL.md - 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 `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:status` - Evaluate when done with `/hub:eval`