team

/team — AgentTeam Orchestrator

Parse the user's input to determine the mode:

Team Mode State

Team mode uses a state file at ~/.claude/.agent-team-active to maintain session continuity. When this file exists, ALL user messages are routed through this skill automatically (via CLAUDE.md rule).

The state file is JSON:

{
  "project_id": "uuid",
  "project_name": "My Project"
}

Mode Detection

First, check if ~/.claude/.agent-team-active exists:

• If it exists AND args start with --stop → Exit Team Mode (delete the file, display "Exited team mode.", STOP)
• If it exists AND no explicit /team invocation (i.e., this was auto-routed by CLAUDE.md) → Continuation Mode
• If it exists AND user explicitly typed /team with new args → proceed to normal mode detection below (the new command takes priority)

Then for explicit /team invocations:

1. If args start with --projects → Project Management Mode
2. If args contain --stop → Exit Team Mode (delete state file, display "Exited team mode.", STOP)
3. If args contain --review → set REVIEW_MODE=true, strip the flag, remaining text is the goal
4. If args have text (after flag removal) → Fast Lane Mode with that text as the goal
5. If no args → Conversational Mode — list projects with numbered selection, then ask for goal

---

Project Management Mode (--projects)

Parse the subcommand after --projects:

• No subcommand → call list_projects via MCP, display with numbered selection grouped by status:

📁 Projects:

   Active
   [1] <name>     (<date>)
   [2] <name>     (<date>)

   Paused
   [3] <name>     (<date>)

   Archived
   [4] <name>     (<date>)

Type a number to focus the team on that project, or /team <goal> to start a new one.

If the user responds with a number, load that project's summary via get_project_summary and ask: "What would you like the team to do on this project?"

If empty: "No projects found."

• active / paused / archived / closed → call list_projects with status filter, display the same format but only the matching group.