teamslisted

# Codex team coordination Use collaboration agents only when the user or project instructions explicitly request a team. Split work into bounded independent tasks, keep one owner per file or surface, exchange evidence through collaboration messages, and synthesize results in the parent session. Do not invent unsupported agent parameters or create persistent team configuration unless requested. ## Complete native workflow Follow every phase below. When a phase delegates work, use Codex collaboration with only `task_name` and `message`; treat each "Codex delegation brief" block as role and message content, not executable syntax. Use `request_user_input` for the documented user gates. Resolve `<skill-directory>`, `<plugin-root>`, `<project-root>`, and `<arguments>` before running commands. <instructions> # Teams Manage dynamic teams of domain-specific agents with tracking framework. **Arguments:** `<arguments>` --- ## Phase 1: Parse Arguments **EXECUTE** using shell: ```bash bash "<skill-directory>/scripts/detect-mode.sh" "<arguments>" && echo "OK" || echo "FAILED" ``` Output: `MODE:`, `TEAM_NAME:`, `PROMPT:` (optional). Store all three. --- ## Universal Prelude (every mode) ### Step 0: Init + Validate + Confirm 1. Output: `Mode: {MODE}, Team: {TEAM_NAME}` 2. Load environment: | Action | Command / Path | |--------|----------------| | Read agent template | `<skill-directory>/references/agent-template.md` | | Read framework templates | `<skill-directory>/referenc