worker

To coordinate OMX team worker lifecycles, this skill manages inbox-based task reading, claim and transition states, and mailbox interactions to ensure predictable collaboration and minimize race conditions among workers.

The ACK-based startup protocol is a standardized readiness flow where a worker pane initializes, acknowledges its worker role, and loads the first assigned task from the inbox to establish predictable team collaboration.

You claim and progress tasks by reading assigned tasks from the inbox, applying the claim and transition lifecycle workflow, and performing state updates via an instruction-driven process within the mailbox interaction framework.

Yes, you need tmux because this skill specifically applies to tmux-based OMX teams where a worker pane must initialize, claim tasks, perform work, and report status within the standardized startup ACK flow.

Race conditions occur when the standardized task lifecycle is not properly applied; implementing the canonical inbox-based task reading and claim transition workflow minimizes these concurrent worker conflicts.

The best way to standardize worker state updates is applying the minimal instruction-driven workflow that manages mailbox interactions and state transitions within the canonical OMX team worker startup protocol.