teamwork

Teamwork Command

Overview

Teamwork enables native agent team collaboration. An orchestrator (team lead) handles the full project lifecycle: planning, spawning workers, coordination, and verification -- all through Claude's native teammate API.

---

Step 0: Serena Project Activation (Optional)

If the MCP tool mcp__plugin_serena_serena__activate_project is available, activate Serena for enhanced code navigation:

# Check if Serena is available and activate
if "mcp__plugin_serena_serena__activate_project" in available_tools:
    try:
        mcp__plugin_serena_serena__activate_project(project=".")
        # Serena enabled - agents can use symbol-based tools
    except:
        pass  # Continue without Serena

Benefits when Serena is active:

• Orchestrator: get_symbols_overview, find_symbol for precise code structure analysis
• Workers: Symbol-based editing tools for safe refactoring

If Serena is not available, agents will use standard tools (Read, Edit, Grep).

---

Step 1: Initialize Project

Execute the setup script:

bun "${CLAUDE_PLUGIN_ROOT}/src/scripts/setup-teamwork.js" $ARGUMENTS

This initializes project metadata and validates the environment (including CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1).

Parse the output to get:

• Project name
• Sub-team name
• Teamwork directory path
• Goal

Step 2: Spawn Orchestrator

The orchestrator is the team lead. It handles the full project lifecycle:

1. Explore the codebase
2. Create tasks with dependencies (TaskCreate + addBlockedBy)
3. Spawn worker teammates (Task with team_name)
4. Coordinate via SendMessage
5. Monitor progress via TaskList
6. Trigger final verification
7. Report project completion

ACTION REQUIRED - Call Task tool with:

• subagent_type: "teamwork:orchestrator"
• model: "opus"
• prompt:

  TEAMWORK_DIR: {teamwork_dir}
  PROJECT: {project}
  SUB_TEAM: {sub_team}
  SCRIPTS_PATH: ${CLAUDE_PLUGIN_ROOT}/src/scripts
  
  Goal: {goal}