How does OmO decide which agents to use?

It uses routing signals based on task clarity and risk. For example, it adds the 'explore' agent if code location is unclear and the 'oracle' agent for high-risk changes involving concurrency or public APIs.

Does OmO write code directly?

No, OmO is strictly an orchestrator; it delegates all code modifications to specialized implementation agents like 'develop' or 'frontend-ui-ux-engineer' to ensure quality.

What is the primary role of the OmO skill?

OmO acts as an orchestrator (persona: Sisyphus) that analyzes your request and routes it to specialized agents for exploration, planning, and implementation.

Can I use OmO for documentation tasks?

Yes, OmO includes a dedicated 'document-writer' agent and can orchestrate the necessary exploration to ensure your documentation accurately reflects the codebase.

OmO Multi-Agent Orchestrator

Name: OmO Multi-Agent Orchestrator
Author: cexll

bycexll

•

1,960

Productivity & Workflow

Orchestrates specialized AI agents to handle complex code analysis, bug investigation, and implementation workflows using a routing-first approach.

About

OmO acts as a high-level manager named Sisyphus that delegates technical tasks to a suite of specialized agents including Explore, Librarian, Oracle, and Develop. Instead of following a rigid pipeline, it evaluates task risk and clarity to route requests through the most efficient path—whether that's a simple one-step fix or a multi-stage investigation and review process. By focusing on context propagation and avoiding direct code modification, OmO ensures that complex repository changes are planned, validated, and executed by the most appropriate specialized tools, minimizing errors and maximizing developer productivity.

Key Features

1,960 GitHub stars
Specialized support for external documentation lookups via the Librarian agent
Dynamic agent routing based on task complexity and risk signals
Context-aware delegation that passes history and requirements between agents
Risk-based architectural review using the Oracle agent for high-impact refactors
Automated handoff to UI/UX or documentation specialists for specific domains

Use Cases

Executing high-risk, multi-file refactors that require a planning and review stage before implementation
Implementing new features that require cross-referencing internal patterns with external API documentation
Investigating and fixing bugs where the root cause or file location is unknown

About

Key Features

1,960 GitHub stars
Specialized support for external documentation lookups via the Librarian agent
Dynamic agent routing based on task complexity and risk signals
Context-aware delegation that passes history and requirements between agents
Risk-based architectural review using the Oracle agent for high-impact refactors
Automated handoff to UI/UX or documentation specialists for specific domains

Use Cases

Executing high-risk, multi-file refactors that require a planning and review stage before implementation
Implementing new features that require cross-referencing internal patterns with external API documentation
Investigating and fixing bugs where the root cause or file location is unknown