oma-orchestration

Orchestrates parallel CLI subagents with memory coordination, verification loops, and retry recovery.

1.3k|146|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/first-fluke/oh-my-agent --skill oma-orchestration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oma-orchestration
Source: https://github.com/first-fluke/oh-my-agent/tree/main/.agents/skills/oma-orchestration
Command: npx skills add https://github.com/first-fluke/oh-my-agent --skill oma-orchestration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Coordinating multiple AI agents on a complex feature is error-prone: agents claim success without proof, tasks overlap, and failures go unnoticed. This Skill automates multi-agent orchestration by decomposing work into priority-tiered tasks, spawning specialist CLI subagents in parallel, and enforcing verification before accepting results.

Core Features & Use Cases

  • Automated Task Decomposition and Dispatch: Breaks a feature request into specialist tasks (backend, frontend, mobile, QA), classifies each into domain tags, and spawns agents via native runtime dispatch or the oma agent:spawn fallback.
  • Iterative Review Loop: Every completed agent passes mechanical self-checks, oma verify, and QA cross-review, with structured feedback fed back on failure and retry limits enforced.
  • Memory-Based Coordination: Uses session, task-board, progress, and result files with strict ownership rules so concurrent agents never conflict.
  • Use Case: Ask to implement a full-stack JWT authentication feature; the orchestrator spawns backend, frontend, and QA agents in parallel, verifies each deliverable, retries failures, and compiles a final summary.

Quick Start

Ask the agent to orchestrate implementing a full-stack feature in parallel, for example: run the authentication feature across backend, frontend, and QA agents automatically.

Frequently Asked Questions about oma-orchestration

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

FAQPage Schema
How do I run multiple AI agents in parallel on one feature?

Request orchestration of the feature and the orchestrator decomposes it into priority-tiered tasks, then spawns specialist CLI subagents in parallel up to the MAX_PARALLEL limit of 3. Each agent works in its own workspace and reports through progress and result files.

How does multi-agent orchestration verify that agents actually finished the work?

Each completed agent passes a mechanical self-check (lint, type-check, tests, diff scope), then `oma verify` for supported agent types, then a QA cross-review. Failures feed structured feedback back to the implementation agent until loop limits are reached.

Which CLI vendors are supported for spawning subagents?

Native dispatch paths exist for Claude Code, OpenCode, Codex CLI, and Gemini CLI. The fallback `oma agent:spawn` path supports configured vendors including claude, codex, qwen, antigravity, cursor, kiro, and pi.

What happens when a subagent keeps failing its review?

After MAX_RETRIES retries with review history, the orchestrator activates an exploration loop that spawns 2-3 alternative hypothesis approaches in parallel workspaces and keeps the highest-scoring result. Final failure is reported with the complete review trail.

When should I not use automated multi-agent orchestration?

Avoid it for simple single-domain tasks, quick bug fixes, or minor changes where a single specialist agent suffices. It is also unsuitable when you want step-by-step manual control, in which case a coordination skill is the better fit.