# Oma Coordination

Coordinate assigned specialist tasks and handoffs manually.

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

## Install

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

## Description

Coordinate assigned specialist tasks and handoffs manually. Use when supervising a multi-agent project step by step.

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

# Multi-Agent Workflow Guide

## Scheduling

### Goal
Guide manual multi-agent coordination for complex work that spans PM, frontend, backend, mobile, and QA responsibilities.

### Intent signature
- User wants step-by-step coordination, manual agent spawning, or multi-domain work planning without full automation.
- Task spans multiple specialist agents and requires contract alignment.

### When to use

- Complex feature spanning multiple domains (full-stack, mobile)
- Coordination needed between frontend, backend, mobile, and QA
- User wants step-by-step guidance for multi-agent coordination

### When NOT to use

- Simple single-domain task -> use the specific agent directly
- User wants automated execution -> use orchestrator
- Quick bug fixes or minor changes

### Expected inputs
- Complex feature or project goal
- Required domains and priority tiers
- Workspace/session constraints and API/data contract needs

### Expected outputs
- Manual coordination sequence
- PM task decomposition, agent spawn order, monitoring guidance, and QA review step
- API/data contract alignment checkpoints

### Dependencies
- PM, frontend, backend, mobile, QA, and orchestrator skills
- CLI `oma agent spawn` and progress/result memory conventions

### Control-flow features
- Branches by task complexity, priority tiers, dependency ordering, and whether automation is desired
- Spawns independent same-priority tasks in parallel when appropriate
- Monitors progress files and contract alignment

## Structural Flow

### Entry
1. Confirm the task is complex enough for multi-agent coordination.
2. Reuse a current plan and handoff state; use PM when task decomposition or contract changes are needed.
3. Identify priority tiers and shared contracts.
4. Apply the shared collaboration policy before assigning parallel work or coordinating ownership handoffs and result collection.

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