team-cli

team-cli

Use team capabilities via a standalone CLI, without relying on channel tool registration.

Hard constraints

• Only allowed to call alex team ...(or go run ./cmd/alex team ... fallback).
• Only flag arguments are allowed; JSON arguments are forbidden.
• Do not use python3 skills/team-cli/run.py(this skill has no run.py).

CLI overview

alex team run ...
alex team status ...
alex team inject ...
alex team terminal ...

If the alex binary is not installed on this machine, use within the repository:

go run ./cmd/alex team run ...
go run ./cmd/alex team status ...
go run ./cmd/alex team inject ...
go run ./cmd/alex team terminal ...

1) Run team (run)

1.1 Execute with a template

alex team run --template claude_research --goal "Compare Postgres logical replication vs CDC for this repo"

1.2 View available templates

alex team run --template list

1.3 Execute with a taskfile

alex team run --file /tmp/team-task.yaml

1.4 Single-prompt task (must be supported)

alex team run --prompt "Audit current branch changes and list top 3 regression risks" --workspace-mode shared

1.5 Common optional parameters

alex team run \
  --template claude_analysis \
  --goal "Evaluate migration strategy" \
  --mode auto \
  --timeout-seconds 900 \
  --session-id sess_manual_001 \
  --role-prompt analyst_a="Focus on correctness" \
  --role-prompt analyst_b="Focus on ops risk"

• --task-id Can be passed repeatedly to restrict execution to a specific task.
• --role-prompt role=prompt Can be passed repeatedly to override role prompts.

2) Query status (status)

alex team status --json
alex team status --all --tail 50 --json
alex team status --session-id sess_manual_001 --json
alex team status --team-id team-executor --json
alex team status --runtime-root .elephant/tasks/_team_runtime --json
alex team --json --all
alex team "帮我看下 team 运行状态"

Parameters (alex team status）：

• --runtime-root: explicit team runtime root directory
• --session-id: filter by session
• --team-id: filter by team
• --all: return all matches (default is latest only)
• --tail: number of events tail entries returned per team (default 20)
• --json: recommended to enable, for structured consumption

3) Inject input (inject)

Inject real input into the tmux pane corresponding to a team role:

alex team inject --task-id analyst_a-1 --message "Continue with stricter evidence and cite files"
alex team inject --role-id analyst_a --message "Focus on replication lag scenarios"
alex team inject --session-id sess_manual_001 --team-id claude_analysis --role-id analyst_b --message "Add operational rollback plan"

Parameters (alex team inject）：

• --runtime-root: explicit runtime root directory
• --session-id: filter session
• --team-id: filter team
• --role-id: target role
• --task-id: derive role automatically from task_id (can replace --role-id）
• --message: injected content (required)

4) Terminal visualization (terminal)

Intuitively view the tmux terminals opened by the team (session or role panes):

alex team terminal --mode attach
alex team terminal --mode capture --lines 200
alex team terminal --task-id team-researcher --mode capture

Parameters (alex team terminal）：

• --runtime-root: explicit runtime root directory
• --session-id: filter session
• --team-id: filter team
• --role-id: specify role pane
• --task-id: derive role automatically from task_id (can replace --role-id）
• --mode: attach|capture|stream(default stream）
• --lines: capture/display line count window (default 120)

Artifact semantics

• Team runtime artifacts are usually located at:
  • .elephant/tasks/_team_runtime
  • .worktrees/**/_team_runtime
• After the run command succeeds, you should continue to use status to read role status, recent events, and path artifacts.