plugins/cache/omc/oh-my-claudecode/4.8.2/skills/omc-teams/SKILL.md
Spawn claude, codex, or gemini CLI workers in tmux panes for parallel task execution
npx skillsauth add moliboy5000/.claude omc-teamsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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).
/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"
claude (Claude CLI), codex (OpenAI Codex CLI), or gemini (Google Gemini CLI)/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"
command -v tmux)$TMUX set, or start/attach tmux first)npm install -g @anthropic-ai/claude-codenpm install -g @openai/codexnpm install -g @google/gemini-cliCheck tmux explicitly before claiming it is missing:
command -v tmux >/dev/null 2>&1
tmux exists but $TMUX is empty, report that the user is not currently inside an active tmux session. Do not say tmux is missing; tell them to start or attach tmux, then rerun.tmux display-message -p '#S'
Extract:
N — worker count (1–10)agent-type — claude|codex|geminitask — task descriptionValidate before decomposing or running anything:
/omc-teams only supports claude, codex, and gemini.expert, explain that /omc-teams launches external CLI workers only./oh-my-claudecode:team instead.Break work into N independent subtasks (file- or concern-scoped) to avoid write conflicts.
Activate mode state (recommended):
state_write(mode="team", current_phase="team-exec", active=true)
Start workers via CLI:
omc team <N>:<claude|codex|gemini> "<task>"
Team name defaults to a slug from the task text (example: review-auth-flow).
After launch, verify the command actually executed instead of assuming Enter fired. Check pane output and confirm the command or worker bootstrap text appears in pane history:
tmux list-panes -a -F '#{session_name}:#{window_index}.#{pane_index} #{pane_id} #{pane_current_command}'
tmux capture-pane -pt <pane-id> -S -20
Do not claim the team started successfully unless pane output shows the command was submitted.
omc team status <team-name>
omc team api list-tasks --input '{"team_name":"<team-name>"}' --json
Use omc team api ... for task claiming, task transitions, mailbox delivery, and worker state updates.
omc team shutdown <team-name>
omc team shutdown <team-name> --force
Use shutdown for intentional cancellation or stale-state cleanup. Prefer non-force shutdown first.
Report task results with completion/failure summary and any remaining risks.
state_write(mode="team", current_phase="complete", active=false)
Legacy MCP runtime tools are deprecated for execution:
omc_run_team_startomc_run_team_statusomc_run_team_waitomc_run_team_cleanupIf encountered, switch to omc team ... CLI commands.
| Error | Cause | Fix |
| ---------------------------- | ----------------------------------- | ----------------------------------------------------------------------------------- |
| not inside tmux | Shell not running inside tmux | Start tmux and rerun |
| Unsupported agent type | Requested agent is not claude/codex/gemini | Use claude, codex, or gemini; for native Claude Code agents use /oh-my-claudecode:team |
| codex: command not found | Codex CLI not installed | npm install -g @openai/codex |
| gemini: command not found | Gemini CLI not installed | npm install -g @google/gemini-cli |
| Team <name> is not running | stale or missing runtime state | omc team status <team-name> then omc team shutdown <team-name> --force if stale |
| status: failed | Workers exited with incomplete work | inspect runtime output, narrow scope, rerun |
/team| Aspect | /team | /omc-teams |
| ------------ | ----------------------------------------- | ---------------------------------------------------- |
| Worker type | Claude Code native team agents | claude / codex / gemini CLI processes in tmux |
| Invocation | TeamCreate / Task / SendMessage | omc team [N:agent] + status + shutdown + api |
| Coordination | Native team messaging and staged pipeline | tmux worker runtime + CLI API state files |
| Use when | You want Claude-native team orchestration | You want external CLI worker execution |
tools
MANDATORY prerequisite — load this skill BEFORE every `generate_diagram` tool call. NEVER call `generate_diagram` directly without loading this skill first. Trigger whenever the user asks to create, generate, draw, render, sketch, or build a diagram — flowchart, architecture diagram, sequence diagram, ERD or entity-relationship diagram, state diagram or state machine, gantt chart, or timeline. Also trigger when the user mentions Mermaid syntax or wants a system architecture, decision tree, dependency graph, API call flow, auth handshake, schema, or pipeline visualized in FigJam. Routes to type-specific guidance, sets universal Mermaid constraints, and tells you when to use a different diagram type or skip the tool entirely (mindmaps, pie charts, class diagrams, etc.).
development
DEFAULT PIPELINE for all tasks requiring execution. You (Claude) are the strategic orchestrator. Codex agents are your implementation army - hyper-focused coding specialists. Trigger on ANY task involving code, file modifications, codebase research, multi-step work, or implementation. This is NOT optional - Codex agents are the default for all execution work. Only skip if the user explicitly asks you to do something yourself.
development
This skill should be used when the user asks to analyze a UI screen recording and map interaction states into Figma. Trigger for requests such as "put video frames in Figma", "extract states from my recording", "map interactions from video to Figma", "analyze this screen recording", "create a storyboard from my video", "deconstruct this interaction in Figma", "annotate the UI states in my recording", or "pull the key moments from this video into Figma". Also trigger when the user references a video file (.mp4, .mov, .webm, .avi) together with Figma, design review, interaction analysis, prototypes, or UI states. The skill extracts key visual moments from a video, infers interaction triggers, and builds an annotated Figma Design storyboard using native Figma annotations and uploaded screenshot assets.
development
Generate a FigJam project plan board from a PRD plus codebase context. Interactive flow: research → propose sections → per-section deep research → per-section content + block-shape proposal → create FigJam → skeleton → fill → diagrams → wrap. Each content block (section, nested section, intro callout, table, multi-column text, sticky column, diagram section, metadata strip) has its own subskill reference file. Use when the user asks for 'project plan in FigJam', 'interactive project plan', '/generate-project-plan', or provides a PRD and wants per-section confirmation on content + rendering.