# Oma Orchestration

Dispatch and supervise parallel specialist agents with durable task state.

- Repository: https://github.com/first-fluke/oh-my-agent (1356 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add first-fluke/oh-my-agent --skill oma-orchestration -g -a claude-code -y`
Codex: `npx skills add first-fluke/oh-my-agent --skill oma-orchestration -g -a codex -y`
Cursor: `npx skills add first-fluke/oh-my-agent --skill oma-orchestration -g -a cursor -y`
Gemini CLI: `npx skills add first-fluke/oh-my-agent --skill oma-orchestration -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add first-fluke/oh-my-agent`

## Description

Dispatch and supervise parallel specialist agents with durable task state. Use when automated multi-agent execution is requested.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Orchestration - Automated Multi-Agent Coordination

## Scheduling

### Goal
Automatically orchestrate multi-agent execution with task decomposition, native/fallback dispatch, memory coordination, progress monitoring, verification, QA cross-review, retry, and result collection.

### Intent signature
- User asks to orchestrate, run in parallel, automate multi-agent execution, or coordinate full-stack work end to end.
- Task requires multiple specialist agents and a persistent review/remediation loop.

### When to use
- Complex feature requires multiple specialized agents working in parallel
- User wants automated execution without manually spawning agents
- Full-stack implementation spanning backend, frontend, mobile, and QA
- User says "run it automatically", "run in parallel", or similar automation requests

### When NOT to use
- Simple single-domain task -> use the specific agent directly
- User wants step-by-step manual control -> use oma-coordination
- Quick bug fixes or minor changes

### Expected inputs
- Complex feature or workflow request
- Project config, model/vendor routing, agent types, task constraints, and workspace/session needs
- Acceptance criteria and verification expectations

### Expected outputs
- Orchestrator session state, task board, progress files, result files, and final summary
- Specialist agent outputs after mechanical checks, automated verify, and QA cross-review
- Review history and retry/remediation status when loops fail

### Dependencies
- `.agents/oma-config.yaml`, `.codex/agents/*.toml`, `.gemini/agents/*.md`, or fallback `oma agent spawn`
- Memory provider config, subagent prompt template, scripts, task templates, verify script, and session metrics

The rest: https://github.com/first-fluke/oh-my-agent/blob/HEAD/.agents/skills/oma-orchestration/SKILL.md