worker

Automate OMX team worker routines by loading this skill to enforce a consistent ACK, mailbox, and task lifecycle across tmux-based team sessions. It standardizes startup acknowledgment, inbox task reading, claiming, execution, and status reporting via prescribed file paths.

The ACK workflow coordinates task lifecycles by requiring workers to acknowledge startup, claim inbox tasks, execute them, and transition states to completed or failed. This ensures orderly handoffs and auditable state changes synchronized through mailbox-based communications.

Standardize task status reporting by using mailbox-based communications to send prescribed messages and state updates. This keeps the OMX team state synchronized and ensures reliable handoffs during the inbox-driven task lifecycle.

Yes, you can enforce orderly task handoffs and state transitions without external dependencies. This skill operates standalone, applying startup ACK, inbox task claims, and file-path-based status updates to manage the OMX worker lifecycle.

OMX worker sessions lack consistency without a standardized protocol for task ownership and state tracking. This skill solves the problem by enforcing an ACK-based startup and a mailbox-driven lifecycle for auditable task transitions.