team-exec

name	team-exec
description	Stage 3/5: Implement approved plan slices with controlled scope and validation notes.

Run OmA team-exec.

Task: $ARGUMENTS

Protocol:

1. Confirm current accepted scope from team-prd.
2. Enforce execution preconditions:
   • require a dependency-aware task graph (team-plan output) and accepted criteria (team-prd output)
   • if either is missing, stop this slice as blocked and route to /oma:team-plan or /oma:team-prd first
3. Read .omg/state/taskboard.md and .omg/state/workspace.json when available, then confirm the active lane owner plus cleanliness/trust notes.
4. Before editing, confirm the lane's expected baseline branch or HEAD anchor when known:
   • if the active branch/HEAD appears to have drifted from the recorded baseline in a way that changes task assumptions, stop this slice as blocked
   • recommend /oma:workspace audit, /oma:team-plan, or explicit branch realignment before continuing
5. Pull only one smallest-ready task slice using deterministic ordering:
   • dependency-ready tasks only
   • lane-safe first (clean + trusted + handoff-ready)
   • highest priority first (p0 -> p1 -> p2 -> p3)
   • stable task id tie-breaker
6. Read target files before editing and preserve existing conventions.
7. Delegate implementation to oma-executor with explicit lane/subagent context.
   • use the current Gemini CLI subagent handoff surface as a unified invocation path; do not assume legacy wrapped subagent tools are available
8. If the requested implementation agent is unavailable (for example "agent not found"), retry once with fallback routing:
   • low-risk slice -> oma-quick
   • architecture-sensitive or high-risk slice -> oma-director for reassignment before retry
   • never loop fallback retries
9. Prefer editing existing files; create new files only when required by accepted scope.
10. Keep each execution slice small and reviewable; keep the success path terse unless the slice stops early or blocks.
11. Record changed files, workspace lane, baseline anchor, rationale, and any early-stop or blocked termination reason.
12. Include checks/tests performed for this slice.
13. If lane health is unsafe for review or automation, call it out and recommend /oma:workspace audit or isolated worktree use.
14. If permissions/tools are denied, stop this slice as blocked and emit explicit approval/fallback needs.
15. Delegated/worker/subagent turns must not write shared workflow state directly.
16. If native Gemini CLI Plan Mode is active, do not activate implementation skills or agent lanes until the user explicitly confirms leaving/readjusting plan-only posture.
17. Read .omg/state/session-lock.json before mutating the shared board.
18. If filesystem tools are available:

• if the current orchestration session owns the lock, update .omg/state/taskboard.md
• otherwise write .omg/state/sessions/[session-slug]/taskboard.md and explicit handoff notes instead of overwriting the shared board

Output format:

Stage

• team-exec

Scope Slice

• task id:
• ...

Execution Outcome

• termination: goal | blocked | stopped-early
• lane:
• baseline:
• subagent:
• route: primary | fallback
• permission: ok | needs-approval | denied

Implementation Log

Change	File(s)	Lane	Baseline	Reason

Validation Signals

• ...

Taskboard Update

• ...

Handoff Notes

• ...

Ready For team-verify

• ...