Spawn Team Skill (Proxy Pattern)

Creates an agent team where the team lead fetches agent configurations from MCP and injects them into teammate prompts. This is required because team agents run in separate tmux sessions and cannot access MCP tools directly.

When to Use

• User requests parallel work across multiple files
• Tasks can be broken into independent units
• Multiple agents needed for efficiency

Proxy Pattern Explained

Problem: Team agents spawned via Task tool with team_name run in separate Claude Code processes. They do NOT inherit MCP server connections and cannot call mcp__agenthub_http__call_agent.

Solution: The team lead (which HAS MCP access) fetches each agent's config BEFORE spawning, then injects the system_prompt into the teammate's prompt.

Workflow Steps