--- name: team description: N coordinated agents on shared task list using Claude Code native teams, with git worktree isolation per executor aliases: [] level: 4 --- # Team Skill Spawn N coordinated agents working on a shared task list using Claude Code's native team tools. Each executor gets its own isolated git worktree to prevent file conflicts. ## Usage ``` /oh-my-claudecode:team N "task description" /oh-my-claudecode:team "task description" ``` ### Parameters - **N** - Number of teammate executors (1-20). Defaults to auto-sizing based on task decomposition. - **task** - High-level task to decompose and distribute among teammates. ## Architecture ``` User: "/team 3 fix all TypeScript errors" | v [TEAM ORCHESTRATOR (Lead)] | +-- TeamCreate("fix-ts-errors") | -> lead becomes team-lead@fix-ts-errors | +-- Analyze & decompose task into subtasks | +-- For each executor: | -> createExecutorWorktree(executorId, teamName, repoRoot) | -> creates .omc/worktrees/{team}/{executor}/ on branch oma-team/{team}/{executor} | +-- TaskCreate x N (one per subtask) | -> tasks #1, #2, #3 with dependencies | +-- TaskUpdate x N (pre-assign owners) | +-- Task(team_name="fix-ts-errors", name="executor-N") x N | -> spawns teammates, each in their own worktree | +-- Monitor loop | +-- On shutdown: -> cleanupTeamWorktrees(teamName, repoRoot) -> removes all executor worktrees and branches ``` ## Git Worktree Isolation Each executor operates in its own git worktree at: ``` {repoRoot}/.omc/worktrees/{teamName}/{executorId}/ ``` With an isolated branch: ``` oma-team/{teamName}/{executorId} ``` ### Worktree Lifecycle 1. **Before spawning**: `createExecutorWorktree(executorId, teamName, repoRoot, baseBranch?)` - Creates worktree directory - Creates and checks out new branch based on `baseBranch` (default: `main`) - Registers worktree in `.omc/state/team-bridge/{teamName}/worktrees.json` 2. **During execution**: Executor operates exclusively in its worktree. No file conflicts with other executors. 3. **After completion**: `removeExecutorWorktree(executorId, teamName, repoRoot)` - Removes worktree - Prunes stale entries - Deletes executor branch 4. **Team shutdown**: `cleanupTeamWorktrees(teamName, repoRoot)` - Removes all executor worktrees for the team - Called automatically on team completion or cancellation ### Worktree Manager API ```javascript import { createExecutorWorktree, removeExecutorWorktree, listWorktrees, cleanupTeamWorktrees, } from './skills/team/worktree-manager.mjs'; // Create worktree for an executor const info = await createExecutorWorktree('executor-1', 'fix-ts-errors', repoRoot, 'main'); // info.path -> /path/to/repo/.omc/worktrees/fix-ts-errors/executor-1 // info.branch -> oma-team/fix-ts-errors/executor-1 // info.executorId -> 'executor-1' // info.teamName -> 'fix-ts-errors' // List active worktrees const paths = listWorktrees('fix-ts-errors', repoRoot); // ['/path/to/repo/.omc/worktrees/fix-ts-errors/executor-1', ...] // Remove a single executor worktree await removeExecutorWorktree('executor-1', 'fix-ts-errors', repoRoot); // Remove all team worktrees (on team shutdown) await cleanupTeamWorktrees('fix-ts-errors', repoRoot); ``` ### Metadata Storage Worktree metadata is persisted at: ``` .omc/state/team-bridge/{teamName}/worktrees.json ``` Format: ```json [ { "path": "/repo/.omc/worktrees/fix-ts-errors/executor-1", "branch": "oma-team/fix-ts-errors/executor-1", "executorId": "executor-1", "teamName": "fix-ts-errors", "createdAt": "2026-04-05T12:00:00.000Z" } ] ``` ### Safety - All paths validated against directory traversal (`..` rejection) - Names sanitized (alphanumeric, hyphen, underscore only) - File locking on metadata writes to prevent concurrent races - Worktrees NOT cleaned up on individual executor shutdown (allows post-mortem inspection) - Full team cleanup only on explicit team shutdown ## Workflow ### Phase 1: Parse Input Extract **N** (agent count, 1-20) and **task** description. ### Phase 2: Analyze & Decompose Break the task into N independent subtasks (file-scoped or module-scoped to avoid conflicts). ### Phase 3: Create Team Call `TeamCreate`: ```json { "team_name": "fix-ts-errors", "description": "Fix all TypeScript errors across the project" } ``` Write OMC state: ``` state_write(mode="team", active=true, current_phase="team-exec", state={ "team_name": "fix-ts-errors", "agent_count": 3, "task": "fix all TypeScript errors", "stage_history": "team-plan" }) ``` ### Phase 4: Create Executor Worktrees For each executor before spawning: ```javascript import { createExecutorWorktree } from '../../skills/team/worktree-manager.mjs'; const worktreeRoot = '/path/to/repo'; for (let i = 1; i <= agentCount; i++) { const executorId = `executor-${i}`; const info = await createExecutorWorktree(executorId, teamName, worktreeRoot, 'main'); // Pass info.path as the workingDirectory for the executor } ``` ### Phase 5: Create Tasks Call `TaskCreate` for each subtask. Pre-assign owners via `TaskUpdate(taskId, owner)` to avoid race conditions. ### Phase 6: Spawn Executors Spawn each executor with their assigned worktree path: ```json { "subagent_type": "oh-my-claudecode:executor", "team_name": "fix-ts-errors", "name": "executor-1", "prompt": "", "workingDirectory": "/repo/.omc/worktrees/fix-ts-errors/executor-1" } ``` **Worker preamble:** ``` You are a TEAM EXECUTOR in team "{team_name}". Your name is "{executor_name}". You are working in an isolated git worktree at {worktree_path}. You report to the team lead ("team-lead"). == WORK PROTOCOL == 1. CLAIM: Call TaskList to see your assigned tasks (owner = "{executor_name}"). Pick the first task with status "pending" that is assigned to you. Call TaskUpdate to set status "in_progress". 2. WORK: Execute the task using your tools (Read, Write, Edit, Bash). Do NOT spawn sub-agents. Do NOT delegate. Work directly in your worktree. 3. COMPLETE: When done, mark the task completed: {"taskId": "ID", "status": "completed"} 4. REPORT: Notify the lead via SendMessage: {"type": "message", "recipient": "team-lead", "content": "Completed task #ID: ", "summary": "Task #ID complete"} 5. NEXT: Check TaskList for more assigned tasks. If no more, notify the lead. 6. SHUTDOWN: When you receive a shutdown_request, respond with: {"type": "shutdown_response", "request_id": "", "approve": true} == RULES == - NEVER spawn sub-agents or use the Task tool - NEVER run team orchestration commands - ALWAYS use absolute file paths - ALWAYS report progress via SendMessage to "team-lead" ``` ### Phase 7: Monitor Monitor progress via inbound `SendMessage` from executors and periodic `TaskList` polling. ### Phase 8: Completion 1. Verify all tasks completed via `TaskList` 2. Shutdown all executors via `SendMessage(shutdown_request)` 3. Call `cleanupTeamWorktrees(teamName, repoRoot)` to remove all worktrees 4. Call `TeamDelete` to clean up team resources 5. Clear OMC team state ## Error Reference | Error | Cause | Fix | |-------|-------|-----| | `git worktree add failed` | Branch/path conflict or git error | Ensure base branch exists; check for path conflicts | | `worktree path not under repo` | Path traversal attempt | Names are sanitized; check executor ID format | | `metadata parse error` | Corrupted worktrees.json | Delete `.omc/state/team-bridge/{team}/worktrees.json` and retry | | `Executor shutdown failed` | Agent did not respond | Use `TeamDelete` with force to clean up | - Tasks require sequential reasoning where later steps depend on earlier results — use ralph instead for a single-agent persistence loop - The task is a single-file change or one-liner — spawning a team is massive overhead - Tasks share mutable state or the same source files — git worktree isolation prevents cross-executor coordination on the same files, but tasks that need to coordinate file changes in real-time will conflict - The codebase is not git-initialized (worktree manager requires git) - User has Auggie context window constraints — team mode generates more orchestration overhead than a single agent - The task is exploratory or research-only (no concrete implementation to parallelize) - **executor**: Each spawned executor works on an assigned subtask in its own git worktree. The orchestrator assigns tasks via TaskCreate/TaskUpdate before spawning. - **planner**: Use before team creation to decompose the task into N independent subtasks that can run concurrently without file conflicts - **architect**: Consult when task decomposition might introduce architectural inconsistencies across parallel work - **qa**: After team execution completes, run a final quality verification pass across all changed files - **Direct git worktree tools**: The worktree manager API (`createExecutorWorktree`, `removeExecutorWorktree`, `cleanupTeamWorktrees`) is called by the team orchestrator itself — no executor should call these directly OMA orchestrates Auggie agents on real codebases. Some tasks are large enough that a single agent taking turns is too slow — e.g., "fix all TypeScript errors" across 50 files, or "audit all skills for missing sections." Team mode provides git worktree isolation so multiple executor agents can work simultaneously on different files without git conflicts, while the team orchestrator handles task distribution, monitoring, and cleanup. The isolation model prevents the most common failure mode of naive parallel execution: two agents modifying the same file. ### Good Usage **Large-scale parallel fix:** ``` User: "/oma:team 4 fix all TypeScript errors" OMA: [Decomposes: 4 executor worktrees, each assigned ~12 files] OMA: [Spawns 4 executor agents, each in its own worktree] OMA: [Monitors — executor 3 reports: "Fixed 8/12 files, 4 need manual review"] OMA: [Shutdown, cleanup] OMA: [Result: 50 TypeScript errors fixed in parallel vs. sequential] ``` **Parallel skills audit:** ``` User: "/oma:team 3 audit all 8 skill directories" OMA: [Decomposes: 3 executors, each auditing ~2-3 skills] OMA: [Each executor writes findings to its own worktree output file] OMA: [Collects: 3 audit reports] OMA: [Integrates into single gap analysis] ``` ### Bad Usage **Sequential dependency hidden as parallel:** ``` User: "/oma:team 2 refactor auth service and update all callers" OMA: [Executor 1: refactors auth.ts in worktree 1] OMA: [Executor 2: tries to update callers in worktree 2 — stale API] OMA: [Result: executor 2 either fails or produces broken code] ``` → Should decompose as a sequential chain: refactor first (1 agent), then update callers (1 agent after refactor completes). **Single-file change:** ``` User: "/oma:team 1 fix the typo in README" OMA: [Spawns 1 executor in a worktree for a README typo] OMA: [Result: massive overhead for a 1-minute task] ``` → Use executor directly. - **Stop and report:** An executor fails to start (worktree creation error) — report the error, do not spawn further executors until resolved - **Stop and reassign:** An executor completes its tasks and another executor's task is still pending — reassign the pending task to the free executor rather than waiting - **Continue with partial:** One executor fails mid-task — report the failure, continue monitoring remaining executors, note which tasks were not completed - **Escalate to user:** All executors fail or all tasks are blocked — present the situation to the user for direction - **Hard stop on user cancel:** Call `cleanupTeamWorktrees` immediately, report partial results - [ ] Task decomposed into N truly independent subtasks (no shared file modifications) - [ ] Base branch confirmed to exist and be clean before creating worktrees - [ ] All executor worktrees created successfully before spawning agents - [ ] Each executor's worktree path passed correctly as `workingDirectory` - [ ] Executor worker preamble includes absolute path instruction and team-lead reporting protocol - [ ] Task list pre-assigned (owners set via TaskUpdate) before spawning to avoid race conditions - [ ] Shutdown signals sent to all executors after TaskList shows all tasks complete - [ ] `cleanupTeamWorktrees` called after all executors confirm shutdown - [ ] Team state cleared (`.oma/state.json` team mode entry removed) - [ ] TeamDelete called to clean up team resources - [ ] Partial results preserved and reported if shutdown was early --- Source attribution: r3dlex Original project: https://github.com/r3dlex/oh-my-auggie/blob/ba105417e37fcae61c12f7b763950ccad29fbc64/plugins/oma/skills/team/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: r3dlex Original project: https://github.com/r3dlex/oh-my-auggie/blob/ba105417e37fcae61c12f7b763950ccad29fbc64/plugins/oma/skills/team/SKILL.md Attribution basis: Source repository record Fields of work: Product Management, Project & Program Management, Sales Roles: Growth Product Manager, Project Manager, Sales Engineer, Sales Development Rep (SDR), Technical Product Manager Specialties: API, Frontend, Git Tools: Bitbucket, GitHub, GitLab Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 98d85b152b0d8af145844d079ecc0fe2e366a95faf131d40fdef2316619622f4