oma-orchestrator

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

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/javiruu/viru-air --skill oma-orchestrator-javiruu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oma-orchestrator
Source: https://github.com/javiruu/viru-air/tree/main/.agents/skills/oma-orchestrator
Command: npx skills add https://github.com/javiruu/viru-air --skill oma-orchestrator-javiruu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Coordinating multiple specialist AI agents on a complex feature manually is slow and error-prone. This Skill automates multi-agent execution by decomposing a request into tasks, spawning CLI subagents in parallel, coordinating them through shared memory files, and enforcing verification and QA review loops before accepting results. ## Core Features & Use Cases - Automated task decomposition and dispatch: Breaks a request into priority-tiered tasks, classifies them into domain tags, and spawns agents via native CLI paths (Claude Code, Codex, Gemini) or the oma agent:spawn fallback. - Memory-based coordination: Uses configurable MCP memory files (session, task board, per-agent progress and result files) with strict ownership rules to prevent write conflicts between concurrent agents. - Iterative review and recovery: Runs mechanical self-checks, oma verify, and QA cross-review loops with retry limits, clarification debt tracking, and escalation when loops are exhausted. - Use Case: Ask to implement a full-stack authentication feature; the orchestrator spawns backend, frontend, and QA agents in parallel, monitors their progress files, verifies each deliverable, and compiles a final summary. ## Quick Start Ask the assistant to orchestrate the implementation of your feature in parallel using the oma-orchestrator, providing the task description, workspace path, and acceptance criteria.

Frequently Asked Questions about oma-orchestrator

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?▼

Define the feature request and let the orchestrator decompose it into priority-tiered tasks, then spawn agents per domain. It dispatches via native CLI paths like `claude --agent` or falls back to `oma agent:spawn`, respecting the MAX_PARALLEL limit.

Which CLI vendors does the orchestrator support for subagents?▼

Supported vendors include Claude Code, Codex CLI, Gemini CLI, Qwen, Cursor, Kiro, and pi, configured in cli-config.yaml. Native dispatch is used when the target vendor matches the current runtime; otherwise the fallback spawn path is used.

How does the orchestrator verify subagent work before accepting it?▼

Each completed agent goes through a mechanical self-check, then `oma verify {agent-type}`, then a QA cross-review. Failures feed back to the implementation agent, with limits of 3 self-check cycles, 2 cross-review rejections, and 5 total iterations.

Can I use a different memory provider than Serena for coordination?▼

Yes, the memory provider is configurable via mcp.json with a memoryConfig block specifying provider, basePath, and tool names for read, write, and edit. The default base path is .serena/memories.

When should I not use multi-agent orchestration?▼

Avoid it for simple single-domain tasks, quick bug fixes, or when you want step-by-step manual control. Use the specific domain agent directly or a manual coordination skill instead.