team

Coordinates durable tmux-based multi-worker tasks with Omagy state and plan-gated execution.

3|Updated May 24, 2026
One-click install
npx skills add https://github.com/shayne-snap/oh-my-antigravity --skill team-shayne-snap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team
Source: https://github.com/shayne-snap/oh-my-antigravity/tree/main/plugin/skills/team
Command: npx skills add https://github.com/shayne-snap/oh-my-antigravity --skill team-shayne-snap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Team solves the need for repeatable, durable multi-worker execution in Antigravity sessions, where work must survive across turns and coordinate safely rather than relying on a single ephemeral prompt.

Core Features & Use Cases

  • Durable agy-only tmux runtime: starts real worker sessions in tmux panes and coordinates them via Omagy state under .omagy/state/team/<team>.
  • Plan-gated, leader-owned execution: executes only from approved plan handoffs (or explicit direct tasks) and ensures the leader validates completion before shutdown.
  • State-first coordination and evidence capture: workers claim progress and evidence through omagy team api, while the runtime verifies startup and stall recovery through structured state checks.

Quick Start

Start a Team from an attached tmux leader pane by running: omagy team 3:implementer "Implement the scoped change described by the task".

Frequently Asked Questions about team

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

FAQPage Schema
How do I coordinate multi-worker execution in tmux without losing state across turns?▼

Durable tmux multi-worker coordination uses an agy-only runtime that starts worker sessions in tmux panes and tracks progress via persistent Omagy state to survive across turns.

What is the best way to orchestrate plan-handoff executions for PRD-driven work decomposition?▼

Plan-handoff executions are orchestrated through a plan-gated, leader-owned runtime that validates approved plans, routes tasks to worker inbox overlays, and confirms completion before shutdown.

How does worktree isolation work when running parallel agent tasks?▼

Worktree isolation for parallel agent tasks is enforced by the team runtime, which routes scoped work to individual worker sessions and validates project working directories to prevent conflicts.

Can I use tmux for durable task coordination and stall recovery in long-running workflows?▼

Tmux durable task coordination verifies startup and manages stall recovery through structured state checks, ensuring workers claim progress and evidence safely via the team API.

Do I need an approved plan to start multi-worker tmux sessions?▼

Approved plan handoffs are required for plan-gated execution, though the runtime also accepts explicit direct tasks when bypassing the standard PRD or test-spec decomposition workflow.

Why does my multi-worker team runtime require duplicate HUD preflight validation?▼

Duplicate HUD preflight validation prevents conflicting head-up displays across worker panes, ensuring the runtime confirms readiness via omagy team status evidence before task routing begins.