| name | team |
| description | In-session OMA multi-worker team — invoke /oh-my-agy:team; plan manifest + coordinate HERE (oma team CLI optional for orchestrator) |
| argument-hint | [manifest path or team goal] |
team (OMA / in-session)
You are already in the agent session
When invoked via /oh-my-agy:team or this team skill, treat $ARGUMENTS as the team goal or manifest path and run leader coordination HERE.
- Do not open with “run
oma team start first” as the only path — author the manifest and plan workers in-session first.
- Canonical slash:
/oh-my-agy:team.
oma team … orchestrator commands live in the Appendix for durable tmux/worktree lifecycle when the user wants managed TeamOrchestrator — not required to draft the plan.
Purpose
Coordinated multi-worker execution (tmux + worktrees + delivery). Explicit only — never implied by ralph/ultrawork. Sibling of OMC/OMX team.
Use when
- User invokes
/oh-my-agy:team or explicitly asks for multi-worker / DAG / worktree team
- Parallel slices need separate write_scopes and deliver/FF publish
Do not use when
- Independent slices in one session without workers →
ultrawork
- Single-agent persistence →
ralph
- Full product pipeline →
autopilot (team only if user opts in during ultragoal)
Leader protocol (in-session)
- Write a valid team manifest (
oma.team-manifest/v1) with DAG deps + write_scope (workspace path under .agy/team/… when used).
- Record workers, claim tokens, worktree paths (tokens shown once when CLI starts the team).
- Workers implement inside write_scope; keep worktree clean for deliver (no leftover runtime files).
- On task complete: commit in worktree → deliver → leader integrates FF.
- Tick starts ready dependents after deps complete.
- Hung workers: supervise + DeadProof reclaim only.
- Stop when done or cancelled (
cancel skill).
Safety
- AuthorityLease blocks overlapping write scopes.
- Dirty worktrees are preserved — never force-clean user work.
- No
git reset --hard / git clean -fd.
- Deliver requires clean porcelain after OMA runtime files are removed (orchestrator does this).
Do not
- Start team without a manifest
- Share one claim token across tasks
- Deliver with dirty unrelated files
- Kill sessions without owner nonce proof
- Imply team from ralph/ultrawork without user opt-in
Final checklist
Appendix: optional oma CLI
Use when the user wants durable TeamOrchestrator (tmux/worktrees):
oma team start --manifest <path> [--mode headless|interactive]
oma team status --team <id>
oma team tick --team <id>
oma team deliver --team <id> --task <id> --claim-token <tok> --generation <n> --worktree <path> --expected-revision <n>
oma team supervise --team <id>
oma team reclaim --team <id> --task <id> …
oma team stop --team <id>
oma team resolve-fork …
In-session plan + artifacts remain the coordination source of truth; CLI owns process lifecycle when started.
