cmux-teamlisted

# cmux-team Boot a **three-tier team** for the current repo in one shot: an **orchestrator lead** on the left, **plan / build / test** workers on the right, each a `Codex` agent, all wired over the cmux socket. **One team = one workspace = one feature.** You drive only the lead; the lead drives the workers. Exact `cmux` CLI syntax and every gotcha live in the **`cmux-orchestration`** skill: consult it first. This skill is only the team-boot recipe layered on top. To swap the agent, replace `Codex` below with `pi` / `codex` / your harness. ## Argument The feature slug is the invocation argument (`/cmux-team checkout-flow`). It names the workspace and the roster file. If none was given, ask for one before doing anything. ## Load-bearing rules (from cmux-orchestration, restated because they bite here) - The team lives in a **new workspace**, which is NOT your caller workspace. **Scope every `new-split` / `send` / `send-key` / `read-screen` on the team with `--workspace "$WS"`**, or you get `not_found`. - `send` types, `send-key enter` submits. Keep them separate for the agent REPLs. - Capture refs from `--json` at creation and thread them through; never guess. Reference the workspace by `workspace:N`, never by name. - Stop a pane with `close-surface`; there is no `close-pane`. ## Step 1 — Preflight: you must be able to reach the socket Drive cmux from a terminal surface INSIDE cmux (default `cmuxOnly`), or from any shell when `automation.socketControlMode` is `password`/