OMC Teams : parallel CLI agents (tmux)

--- name: omc-teams description: CLI-team runtime for claude, codex, or gemini workers in tmux panes when you need process-based parallel execution aliases: [] level: 4 --- # OMC Teams Skill Spawn N CLI worker processes in tmux panes to execute tasks in parallel. Supports claude, codex, and gemini agent types. /omc-teams is a legacy compatibility skill for the CLI-first runtime: use omc team ... commands (not deprecated MCP runtime tools). ## Usage ``bash /oh-my-claudecode:omc-teams N:claude "task description" /oh-my-claudecode:omc-teams N:codex "task description" /oh-my-claudecode:omc-teams N:gemini "task description" ` ### Parameters - **N** - Number of CLI workers (1-10) - **agent-type** - claude (Claude CLI), codex (OpenAI Codex CLI), or gemini (Google Gemini CLI) - **task** - Task description to distribute across all workers ### Examples `bash /omc-teams 2:claude "implement auth module with tests" /omc-teams 2:codex "review the auth module for security issues" /omc-teams 3:gemini "redesign UI components for accessibility" ` ## Requirements - **tmux binary** must be installed and discoverable (command -v tmux) - **Classic tmux session optional** for in-place pane splitting ($TMUX set). Inside cmux or a plain terminal, omc team falls back to a detached tmux session instead of splitting the current surface. - **claude** CLI: npm install -g @anthropic-ai/claude-code - **codex** CLI: npm install -g @openai/codex - **gemini** CLI: npm install -g @google/gemini-cli ## Workflow ### Phase 0: Verify prerequisites Check tmux explicitly before claiming it is missing: `bash command -v tmux >/dev/null 2>&1 ` - If this fails, report that **tmux is not installed** and stop. - If $TMUX is set, omc team can reuse the current tmux window/panes directly. - If $TMUX is empty but CMUXSURFACEID is set, report that the user is running inside **cmux**. Do **not** say tmux is missing or that they are "not inside tmux"; omc team will launch a **detached tmux session** for workers instead of splitting the cmux surface. - If neither $TMUX nor CMUXSURFACEID is set, report that the user is in a **plain terminal**. omc team can still launch a **detached tmux session**, but if they specifically want in-place pane/window topology they should start from a classic tmux session first. - If you need to confirm the active tmux session, use: `bash tmux display-message -p '#S' ` ### Phase 1: Parse + validate input Extract: - N : worker count (1:10) - agent-type : claude|codex|gemini - task : task description Validate before decomposing or running anything: - Reject unsupported agent types up front. /omc-teams only supports **claude**, **codex**, and **gemini**. - If the user asks for an unsupported type such as expert, explain that /omc-teams launches external CLI workers only. - For native Claude Code team agents/roles, direct them to **/oh-my-claudecode:team** instead. ### Phase 2: Decompose task Break work into N independent subtasks (file- or concern-scoped) to avoid write conflicts. ### Phase 2.5: Resolve workspace root for multi-repo plans omc team launches all workers with one shared working directory. For single-repo tasks, the current repo is usually correct. For multi-repo tasks, especially when a plan lives in one repo but the implementation touches sibling repos, resolve the working directory before launch: - If the task references a plan artifact under one repo (for example tool/.omc/plans/task-1200-gwd-gifs.md) and target paths in sibling repos (for example api/ and admin/), choose the shared workspace root that contains all participating repos (for example the parent inter/ directory). - Use an **absolute plan path** in the task text so the workers can still find the plan after --cwd changes the launch directory. - Include the explicit repo paths or repo names in the task text and subtasks. - Do not anchor the launch cwd to only the repo containing .omc/plans/... when target repos are siblings; that strands codex, claude, and gemini workers in the plan repo instead of the implementation workspace. - If no safe shared workspace root can be identified, do not launch /omc-teams. Report the single-cwd constraint and ask for, or derive from evidence, the intended workspace root. ### Phase 3: Start CLI team runtime Activate mode state (recommended): `text state_write(mode="team", current_phase="team-exec", active=true) ` Start workers via CLI: `bash omc team <N>:<claude|codex|gemini> "<task>" ` For the multi-repo case resolved in Phase 2.5, launch from the shared workspace root with the existing --cwd contract and keep the plan reference absolute: `bash omc team <N>:<claude|codex|gemini> "<task with absolute plan path and explicit repo paths>" --cwd <workspace-root> ` Team name defaults to a slug from the task text (example: review-auth-flow`). After launch, veri