team

name	team
description	Run OmA's full team lifecycle with optional dynamic team assembly and verify/fix loops.

Coordinate the request with OmA agents.

Task: $ARGUMENTS

Execution protocol (staged):

1. If team composition is unclear or task is non-standard, run team-assemble first.
2. Read .omg/state/session-lock.json, then load .omg/state/workspace.json and .omg/state/reasoning.json when available.
3. Identify the immediate blocking objective and keep it on the active critical lane.
4. team-plan: Delegate decomposition to oma-planner and architecture checks to oma-architect, including lane-health and isolation risks.
5. team-prd: Delegate scope lock and acceptance criteria to oma-product.
6. taskboard: Sync compact task ledger before first implementation slice (priority-aware with null-safe default p2).
7. Keep lane baseline branch/HEAD anchors explicit across plan -> prd -> exec -> verify handoffs when workspace/taskboard state can carry them.
8. team-exec: Delegate implementation slices to oma-executor with explicit lane/subagent context and terse success reporting.
9. team-verify: Delegate validation to oma-reviewer and oma-verifier (include anti-slop quality check plus lane/handoff evidence).
10. team-fix: If verification fails, delegate root-cause and patches to oma-debugger + oma-executor.
11. Repeat steps 8-10 until acceptance criteria pass, all tracked tasks are verified, or blockers are explicit.
12. If an assigned implementation/review agent is unavailable ("agent not found"), retry once using a mapped fallback lane and record the reroute reason.
13. If permissions/tools are denied, do not retry unchanged commands; mark blocker and route to explicit approval or fallback path.
14. Return one merged lifecycle report.

State handling:

• Only the orchestration session that owns .omg/state/session-lock.json may update shared workflow artifacts.
• If another session owns the lock, do not overwrite .omg/state/workflow.md, .omg/state/taskboard.md, or .omg/state/workspace.json; write session-local drafts under .omg/state/sessions/[session-slug]/ and report merge needs.
• If filesystem tools are available and the current session owns the lock, update .omg/state/workflow.md with stage status and open blockers.
• Keep .omg/state/taskboard.md as the compact source of truth for ready, blocked, done, and verified tasks only for the lock-owning orchestration session.
• Keep task ordering deterministic via dependency-ready + lane-safe + priority (p0 -> p3) + task-id tie-breaker.
• Keep .omg/state/workspace.json as the compact source of truth for lane ownership, cleanliness, trust, and handoff readiness only for the lock-owning orchestration session.
• Preserve lane baseline anchors in both workspace/taskboard state when known so resume and review can detect branch drift.
• If dynamic assembly was used, also persist .omg/state/team-assembly.md.
• Keep verification evidence concise (tests, checks, reasoning) and avoid repeating full success traces when nothing unusual happened.

Final report format:

• Keep it concise and operator-facing.
• Include Pipeline Summary, Team Assembly, Critical Path Status, Stage Results, Work Completed, Validation, and Open Items.
• Collapse stage details when a stage was skipped, unchanged, or ended on the normal success path; expand only blocker or early-stop branches.