What problem does it solve? Coordinating multiple AI coding agents on a shared task list is error-prone when done through ad-hoc terminal typing. This Skill provides a structured operator workflow for launching, monitoring, and shutting down N parallel Codex or Claude CLI workers in tmux panes, coordinated through durable state files and mailbox-based messaging instead of fragile keystroke injection. ## Core Features & Use Cases - Parallel worker orchestration: Launch N workers with role prompts via omx team N:agent-type "<task>", with per-worker CLI selection (Codex or Claude) and optional git worktree isolation. - State-first coordination: Tasks, mailboxes, heartbeats, and dispatch queues live under .omx/state/team/<team>/, mutated through the omx team api ... --json CLI rather than direct tmux send-keys. - Lifecycle contract: Enforces startup verification, active leader monitoring loops, terminal-state gating before shutdown, and clean-slate recovery for stale panes. - Use Case: A developer needs three workers to analyze a feature, fix bugs, and run verification in parallel. They run omx team 3:executor "analyze feature X and report flaws", monitor with omx team status, and shut down only after all tasks reach terminal state. ## Quick Start Ask the agent to launch a coordinated team by running omx team with a worker count, role, and task description, then monitor progress with omx team status until all tasks complete.