phone-a-teamlisted

# /phone-a-team for Codex Iterative multi-model refinement loop. Use this when the user wants more than a single relay — they want backends to push back on each other across rounds and converge on something. For one-shot "ask X and Y" requests, use `/phone-a-friend` (which already supports parallel multi-backend) instead. You orchestrate the rounds yourself via Bash. Do not spawn Codex subagents for this — the skill is designed to run end-to-end in the parent turn. Codex's own model does the synthesis between rounds by reading the per-backend outputs you write to disk. ## Inputs `$ARGUMENTS` contains the user's request. Parse: - **TASK_DESCRIPTION**: free-form text with flags stripped. - **`--backend <name>`** (or `--backend a,b`): comma-separated list of friend backends to query each round. Allowed: `claude`, `gemini`, `opencode`, `ollama`. **Never** `codex` (the recursion guard refuses; you would be calling yourself). Default: `claude,gemini`. `antigravity` is deliberately excluded until the PaF backend supports session continuity; `/phone-a-friend` supports one-shot Antigravity relays. - **`--max-rounds N`**: rounds before giving up. Clamp to [1, 5]. Default: 3. - **`--model <name>`**: only meaningful for `ollama` and `opencode`. If the user named only one backend, the team degenerates to a self-review loop against that backend across rounds. That is valid; do not error out, just proceed. ## Step 0 — Preflight 1. Resolve the binary. **Always** use the PATH-installe