From spawn-team
Use this skill whenever the user asks to spin up a team of agents, use split panes, run agents in parallel with coordination, or mentions 'swarm'. Also use proactively when a task would clearly benefit from multiple coordinated agents working in split panes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/spawn-team:spawn-teamThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Spin up a coordinated team of agents that appear in split panes in the terminal UI.
Spin up a coordinated team of agents that appear in split panes in the terminal UI.
Plain Agent tool calls do NOT create split panes — they run as background subagents. To get split panes, you MUST:
TeamCreateteam_name parameter set to the team name$ARGUMENTS (optional):
Use TeamCreate with a descriptive team name:
TeamCreate:
team_name: "<descriptive-kebab-case-name>"
description: "<what the team is working on>"
Use the Agent tool for each agent, always including:
team_name: must match the team name from Step 1name: a short kebab-case name for the agent (used for messaging)prompt: clear instructions for what the agent should doSpawn all agents in parallel (multiple Agent tool calls in one message) for them to appear as split panes simultaneously.
Agent:
name: "agent-name"
team_name: "<team-name>"
prompt: "<task instructions>"
SendMessage (type: "message" for DMs, "broadcast" for all)TaskCreate / TaskUpdate if neededWhen work is done:
shutdown_request to each agent via SendMessageTeamDelete to clean up team and task directoriesAgent calls without team_name — no split panes will appearTeamCreate before spawning agentsrun_in_background: true with team agents — they manage their own lifecycleSendMessage for all inter-agent communication (plain text output is not visible to teammates)npx claudepluginhub winsthuang/hazel-skills --plugin spawn-teamCreates named agent teams in tmux split panes with specialized persistent teammates for visible collaboration on complex tasks, bypassing background subagents.
Guides composing agent teams for complex tasks with predefined roles: Orchestrator, Explorer, Frontend (React), Backend (Rails), iOS/Swift, Android/Kotlin, Database.
Orchestrates multi-agent teams to decompose complex tasks, select optimal sub-agents like Explore or Plan, and execute parallel work across domains such as frontend and backend.