agent-doc-discipline
Writing-time discipline for documents agents consume (the five surfaces, specs, tickets, .omc/skills/) — every rule checkable and carrying a why, steps before…
N coordinated agents on shared task list using Claude Code implicit agent teams
$ npx -y skills add Yeachan-Heo/oh-my-claudecode --skill team --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/teamContext preview
The summary Claude sees to decide when to auto-load this skill.
N coordinated agents on shared task list using Claude Code implicit agent teams
name: team description: N coordinated agents on shared task list using Claude Code implicit agent teams argument-hint: "[N:agent-type] [ralph] <task description>" aliases: [] level: 4
Spawn N coordinated agents working on a shared task list using Claude Code's implicit agent team. Claude Code 2.1.178+ removed native `TeamCreate`/`TeamDelete`; with `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1`, each session has one implicit team and teammates are spawned directly with the Agent/Task tool using distinct `name` values. This skill still preserves OMC's legacy tmux/CLI worker orchestration where documented (`omc team` / `/omc-teams`).
The `swarm` compatibility alias was removed in #1131.
/oh-my-claudecode:team N:agent-type "task description" /oh-my-claudecode:team "task description" /oh-my-claudecode:team ralph "task description"
/team 5:executor "fix all TypeScript errors across the project" /team 3:debugger "fix build errors in src/" /team 4:designer "implement responsive layouts for all page components" /team "refactor the auth module with security review" /team ralph "build a complete REST API for user management" # With Codex CLI workers (requires: npm install -g @openai/codex) /team 2:codex "review architecture and suggest improvements" # With Gemini CLI workers (requires: npm install -g @google/gemini-cli) /team 2:gemini "redesign the UI components" # With Antigravity CLI workers (requires: install per https://antigravity.google) /team 2:antigravity "redesign the UI components" # Mixed: Codex for backend analysis, Gemini/Antigravity for frontend (delegate per-task with /oh-my-claudecode:ask)
User: "/team 3:executor fix all TypeScript errors"
|
v
[TEAM ORCHESTRATOR (Lead)]
|
+-- Use the session's implicit Claude Code team
| -> no TeamCreate call; lead remains current session
|
+-- Analyze & decompose task into subtasks
| -> explore/architect produces subtask list
|
+-- Create task list entries from the implementation plan
| -> TODO/task entries #1, #2, #3 with dependencies
|
+-- Update task-list entries (pre-assign owners)
| -> task #1 owner=worker-1, etc.
|
+-- Task(name="worker-1") x 3
| -> spawns teammates into the team
|
+-- Monitor loop
| <- teammate messages (auto-delivered by the active team surface)
| -> task-list/TodoWrite review for progress
| -> message teammates through the active team surface to unblock/coordinate
|
+-- Completion
-> request shutdown from each teammate through the active team surface
<- shutdown acknowledgement from teammates
-> clear OMC team state (no TeamDelete call)
-> rm .omc/state/team-state.json**Native Claude Code team model (2.1.178+):**
- No per-team ~/.claude/teams/<name>/ directory is created by this skill. - No TeamCreate/TeamDelete calls are available. - `team_name` is accepted by native Claude Code only as ignored legacy metadata; do not rely on it for routing. - Spawn teammates directly via Agent/Task with `name="worker-N"`.
Team is the OMC authority for parallel, staged execution. Use the deterministic conflict policies `refuse`, `adopt_existing`, and `artifact_only` rather than non-deterministic warning handling. If a task mentions Claude Code `/goal`, Ralph, or artifact-only Ultragoal, keep Team as the primary loop authority unless the leader explicitly hands off. Use `/goal` only as a documented native Claude Code handoff target or as visible evidence from the lead session; do not claim the `/goal` evaluator independently runs commands, reads files, or replaces `team-verify` / `team-fix`. Artifact-only Ultragoal references should be treated as durable goal ledger/checkpoint/evidence artifacts, not as worker execution by themselves.
Team execution follows a staged pipeline:
`team-plan -> team-prd -> team-exec -> team-verify -> team-fix (loop)`
Each pipeline stage uses **specialized agents** -- not just executors. The lead selects agents based on the stage and task characteristics.
| Stage | Required Agents | Optional Agents | Selection Criteria | | --------------- | ----------------------------------- | ------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------
For Codex users: Check out oh-my-codex — the same orchestration experience for OpenAI Codex CLI. Liked OmC but found it a bit overkill? Try gajae-code.
Repo: Yeachan-Heo/oh-my-claudecode
Writing-time discipline for documents agents consume (the five surfaces, specs, tickets, .omc/skills/) — every rule checkable and carrying a why, steps before…
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode
Shipyard's navigator — chart a foggy effort (destination unclear, questions not yet stateable) into a map of decision tickets on the repo's issue tracker, then…
Process-first advisor routing for Claude, Codex, Gemini, Antigravity, Grok, or Cursor via `omc ask`, with artifact capture and no raw CLI assembly
Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior