DOCS · REFERENCE · COMMANDS · BUILD

list-teams/synthex:list-teams

Build

List running standing review pools and per-invocation teams, with composition and load.

Invocation

Run from inside Claude Code in any project where Synthex is installed:

/synthex:list-teams

Some commands accept parameters; see the source-of-truth file linked below for the full parameter list and workflow.

Lifecycle phase

Build. Parallel-executed, peer-reviewed task delivery.

  • Tech Lead · Full-stack orchestrator. Breaks tasks down, delegates to specialists, rolls up the result.
  • Lead Frontend Engineer · Coordinates frontend delivery, enforces UX quality, accessibility, and design-system fidelity.
  • Architect · System design, ADRs, plan-review feasibility, technology trade-offs.
  • Code Reviewer · Craftsmanship review — correctness, maintainability, reuse, conventions.
  • Security Reviewer · Mandatory gate. Secrets, injection, auth, supply chain, OWASP.
  • Quality Engineer · Test strategy, gap analysis, behavior-driven test authoring.
  • Design System · Token ownership, component governance, compliance audit.
  • Technical Writer · API docs, guides, migrations, changelogs verifiable against code.

Source

The command's parameters, workflow, and sub-agent invocations are defined in markdown at bluminal/lumenai/blob/main/plugins/synthex/commands/list-teams.md.

Last modified:

What it does, end-to-end

list-teams/synthex:list-teams shows every standing review pool on this machine, plus any other Agent Teams team directories it finds under ~/.claude/teams/. It takes no arguments and is read-only.

Standing pools come from ~/.claude/teams/standing/index.json. An index entry whose metadata directory no longer exists is stale and quietly left out.

Like the other pool commands, it needs the Agent Teams tools (SendMessage and ListAgents) and stops with a notice on hosts without them.

Output format

Standing pools:
  Name           State     Roster                              Multi-Model  Tasks (pending/in-progress/completed)  Idle    TTL Remaining
  review-pool    idle      code-reviewer, security-reviewer    yes          0 / 0 / 47                              12 min  48 min
  bg-pool        draining  code-reviewer, security-reviewer    no           0 / 1 / 12                              0 min   0 min

Non-standing teams:
  Name              Roster                                                           Tasks                  Started
  review-a3f7b2c1   code-reviewer, security-reviewer, design-system-agent           1 / 0 / 0              2 min ago
  • Standing pools come first, then other teams. Each section is sorted by name and left out when empty.
  • Idle is minutes since the pool last did work.
  • TTL Remaining is the pool's ttl_minutes minus its idle time, never below 0, always in whole minutes. It reads 0 for a pool that's draining or stopping.

Below the tables, a short key explains the four pool states:

StateMeaning
idleNo reviews pending or in progress. Available for routing.
activeReviews pending or in progress. Still available for routing.
drainingFinishing in-flight reviews before shutdown. Not accepting new work.
stoppingShutdown sent, waiting for confirmation. Will disappear shortly.

With nothing running, it prints a one-line hint to start a pool with

start-review-team/synthex:start-review-team.

Common scenarios

"A pool shows 0 min TTL remaining but it's still listed"

TTL is enforced lazily. An expired pool isn't killed on a timer; routed reviews just stop using it, and stale pools are cleaned up the next time a review goes looking for one. Stop it yourself with stop-review-team/synthex:stop-review-team if you want it gone now.

"A pool is stuck in draining"

It's finishing reviews that were already in progress. To end it now, run /synthex:stop-review-team --name <name> --force.

See also

  • Standing review pools
  • start-review-team/synthex:start-review-team — start a pool
  • stop-review-team/synthex:stop-review-team — stop a pool