teammode
Orchestrates a named team of cooperating Codex agents with durable on-disk state, choosing between native MultiAgentV2 agents and Codex App threads, and handles spawning, communication, worktrees, int
What it does
Codex-only team orchestration: run a named team of cooperating Codex workers with durable, script-managed state. MUST USE when the user asks Codex to create, run, coordinate, inspect, archive, or delete a team of agents/threads/sessions, or to work on something as a team in parallel. FIRST inspects the active tool surface (checking tool_search for deferred tools) and tells the user the route: native MultiAgentV2 agents (flat spawn_agent with task_name) when available, Codex App threads as the fallback, or a plain-subagent split when neither set exists. The main session is always the leader; members are defined by a concrete part, ownership area, or perspective - never a vague job role; a bundled cross-platform script writes the .omo/teams state plus an auto-generated member field manual. Use a team when the work is not perfectly isolated but parallelizing helps; use plain subagents when scope is perfectly isolated or the goal is ambiguous. Triggers: team mode, teammode, make a team, run as a team, team of agents, coordinate threads, parallel Codex threads, archive the team.
Quality judgment
An exceptionally thorough, well-organized skill: explicit transport-selection decision tree, leader/composition rules, full script command reference, communication and worktree protocols, lifecycle (archive/delete) with stop rules, and a rich trigger list with MUST-USE language. Minor deductions for reliance on external 'ultrawork directive'/'Task resources' sections that may not be present, and dense prose that occasionally buries key rules.