team

Orchestrate OMX team execution across tmux panes with durable state management.

24|2|Updated Mar 12, 2025
One-click install
npx skills add https://github.com/Orinks/AccessiWeather --skill team-orinks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team
Source: https://github.com/Orinks/AccessiWeather/tree/main/.codex/skills/team
Command: npx skills add https://github.com/Orinks/AccessiWeather --skill team-orinks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OMX enables teams to run and coordinate multiple worker agents on a shared task list using a tmux-based orchestration model, simplifying complex parallel workflows and reducing manual setup.

Core Features & Use Cases

  • Orchestrates coordinated OMX team execution across multiple tmux panes with durable state management and worker coordination.
  • Guides safe startup, monitoring, and shutdown of team-driven tasks, including "leader" and "worker" roles, messages via mailbox and task state files.
  • Use Case: A software engineering collaboration where a leader coordinates several subtasks (analysis, data collection, validation) across multiple workers to complete a feature.

Quick Start

Launch OMX team with a task description to start coordinated worker panes in tmux.

Frequently Asked Questions about team

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate multiple parallel workers in tmux?

Parallel worker coordination in tmux is handled by orchestrating OMX team execution across multiple panes with durable state management. It assigns leader and worker roles, utilizing mailbox messages and task state files to synchronize concurrent subtasks safely.

What is OMX team execution for software engineering collaboration?

OMX team execution is a tmux-based orchestration model that runs multiple worker agents on a shared task list. It automates complex parallel workflows by managing worker startup, monitoring, and strict process lifecycle rules through a structured leader-worker hierarchy.

How do I start a coordinated team task using the omx team command?

Start a coordinated team task by launching OMX team with a task description to initialize coordinated worker panes in tmux. This triggers launcher orchestration via the 'omx team' command, generating state files under .omx/state/team and worker inboxes for execution.

Does this parallel execution approach require specific state files for worker coordination?

Yes, this parallel execution approach requires state files under .omx/state/team to manage durable worker coordination. It also utilizes worker inboxes for interprocess communication and heartbeats to actively monitor the strict process lifecycle of each worker.

What's the best way to manage leader and worker roles for parallel subtasks?

Managing leader and worker roles for parallel subtasks is best handled through a tmux-based orchestration model. The leader coordinates task delegation and lifecycle monitoring, while workers execute subtasks concurrently, communicating via mailbox and task state files.

When should I not use tmux pane orchestration for parallel agent workflows?

Avoid tmux pane orchestration for parallel agent workflows if your environment lacks tmux or requires non-durable, stateless execution. This approach strictly depends on tmux, durable state files under .omx/state/team, and strict process lifecycle rules for safe worker coordination.