team-status — Claude Code command: agent team status at a glance
Shows the members, task state and progress of an active agent team. Useful when several subagents are working on the same project.
/plugin marketplace add wshobson/agents
/plugin install agent-teams@claude-code-workflowsWhat team-status does
The command reads the team config from ~/.claude/teams/{team-name}/config.json and calls TaskList for the current task state. It then prints two tables: members with their roles and status, and tasks with ID, owner and subject. Progress lands at the bottom as a percentage and a completed count.
You can skip the team name. In that case it checks ~/.claude/teams/ and, if several teams are active, lists them and asks you to pick one. The --tasks and --members flags narrow the output to a single table, while --json returns the raw config and task list as JSON — handy when another script has to consume the result.
One catch: with no config.json in the team directory there is nothing to display, so make sure the team exists where the command expects it. And --json replaces the formatted tables entirely, so it is the wrong flag for reading by eye.
What it helps with
- see which subagents are busy and which are idle
- check which tasks are still unassigned
- gauge how much of the team's work is done
- export team state as JSON for an external script
- find the right team when several exist in the directory
Example prompts for the agent
- /team-status
- /team-status security-team --tasks
- /team-status --json
How to install team-status
1Plugin marketplace
/plugin marketplace add wshobson/agents/plugin install agent-teams@claude-code-workflows2Manually: put the files in place
.claude/commands/team-status.mdCall it with /team-status. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/team-status.mdCall it with /prompts:team-status. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/team-status.prompt.mdManually: put the files in place
.gemini/commands/team-status.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about team-status
How do I install team-status in Claude?
Through the marketplace: first /plugin marketplace add wshobson/agents, then /plugin install agent-teams@claude-code-workflows.
What does team-status do?
It lists the members of an active agent team with their roles and status, plus tasks with owners and dependencies. Progress across completed tasks is shown at the end.
What does the command need to work?
A ~/.claude/teams/{team-name}/config.json file with the team config. Without a team name it scans ~/.claude/teams/ and asks you to choose.
Source text
team-status.md · MIT
---
description: "Display team members, task status, and progress for an active agent team"
argument-hint: "[team-name] [--tasks] [--members] [--json]"
---
# Team Status
Display the current state of an active agent team including members, tasks, and progress.
## Phase 1: Team Discovery
1. Parse `$ARGUMENTS` for team name and flags:
- If team name provided, use it directly
- If no team name, check `~/.claude/teams/` for active teams
- If multiple teams exist and no name specified, list all teams and ask user to choose
- `--tasks`: show only task details
- `--members`: show only member details
- `--json`: output raw JSON instead of formatted table
2. Read team config from `~/.claude/teams/{team-name}/config.json` using the Read tool
3. Call `TaskList` to get current task state
## Phase 2: Status Display
### Members Table
Display each team member with their current state:
```
Team: {team-name}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Members:
Name Role Status
─────────────────────────────────────────
security-rev team-reviewer working on task #2
perf-rev team-reviewer idle
arch-rev team-reviewer working on task #4
```
### Tasks Table
Display tasks with status, assignee, and dependencies:
```
Tasks:
ID Status Owner Subject
─────────────────────────────────────────────────
#1 completed security-rev Review auth module
#2 in_progress security-rev Review API endpoints
#3 completed perf-rev Profile database queries
#4 in_progress arch-rev Analyze module structure
#5 pending (unassigned) Consolidate findings
Progress: 40% (2/5 completed)
```
### JSON Output
If `--json` flag is set, output the raw team config and task list as JSON.
© Seth Hobson · MIT · wshobson/agents