Omx Product Team

Purpose

Use this skill when the OMX plugin bundle is installed and the work needs durable orchestration rather than one-shot fanout. It is for queueing slices, assigning workers, collecting handoffs, and holding review state across sessions.

Use When

• the work splits cleanly into multiple slices
• workers need claims, leases, inbox messages, or review handoffs
• the runtime must survive longer than one local reasoning burst

Do Not Use When

• the task is serial and small
• there is no real slice boundary
• the review overhead would exceed the value of parallelism

Workflow

1. Initialize runtime state with omx team init.
2. Spawn or attach workers with omx team spawn <workerId>.
3. Queue explicit slices with concrete outcomes.
4. Claim tasks through worker ids, not ad-hoc ownership.