New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Manual Multi-Agent Coordination

by first-fluke in first-fluke/oh-my-agent

Guides step-by-step coordination of PM, frontend, backend, mobile and QA agents on a complex project, with priority tiers, contract checks and QA review.

MITAuto-check passedAgent Workflows

Install Manual Multi-Agent Coordination

skills CLI
$ npx skills add first-fluke/oh-my-agent --skill oma-coordination -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install first-fluke/oh-my-agent oma-coordination --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/benchmarks/runs/oma/.agents/skills/oma-coordination .claude/skills/oma-coordination && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
oma-coordination
GitHub stars
1.3k
Token cost
~1.4k tokens
SKILL.md length
621 words
Files
2
Skills in repo
57
Repo updated
First seen
Licence
MIT

At a glance

Guides step-by-step coordination of PM, frontend, backend, mobile and QA agents on a complex project, with priority tiers, contract checks and QA review.

  • Works in 4 steps: Plan with PM Agent → Spawn Agents by Priority → Monitor & Coordinate → …
  • Building a feature that spans frontend, backend, mobile and QA work
  • SKILL.md covers Scheduling, Structural Flow and Logical Operations
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

This skill guides manual coordination of several specialist agents on a complex project that spans product management, frontend, backend, mobile and QA. It is meant for step-by-step control rather than full automation, and it tells the agent to send simple single-domain tasks to one specialist, quick fixes to normal handling and automated runs to the orchestrator skill.

The flow runs in four stages. Prepare defines the session, domains and task decomposition, starting with a product-manager breakdown, priority tiers and shared API or data contracts. Act spawns agents by priority with the `oma agent:spawn` command in separate workspaces, running independent same-priority tasks in parallel. Verify monitors progress files and contract alignment. Finalize runs a QA review and coordinates fixes, re-spawning the responsible agents if critical issues turn up.

Recovery rules cover three cases: if contracts diverge, downstream frontend and mobile work pauses until the backend contract is settled; if workspaces conflict, ownership boundaries are split; if progress stalls, the agent inspects the progress files and reissues focused instructions. A file at `resources/examples.md` holds worked examples.

When your agent uses it

  • Building a feature that spans frontend, backend, mobile and QA work
  • Wanting step-by-step control over when each specialist agent starts
  • Keeping API contracts aligned between agents working in parallel

Example prompts

  • “Coordinate the PM, backend, frontend and QA agents to build the invoice export feature, one step at a time.”
  • “Break this mobile and web feature into priority tiers and tell me which agents to spawn first.”
  • “The frontend and backend agents disagree on the API response shape. Pause and reconcile the contract.”

Requirements

  • The `oma` CLI with its PM, frontend, backend, mobile, QA and orchestrator skills

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Plan with PM Agent
  2. Spawn Agents by Priority
  3. Monitor & Coordinate
  4. QA Review

What it can do on your machine

Read from SKILL.md and the folder at commit f65bbc0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Manual Multi-Agent Coordination loads about 1.4k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 621 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~44
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from first-fluke/oh-my-agent at commit f65bbc0, republished under its MIT licence (© first-fluke). 621 words, ~1,432 tokens.

Download SKILL.mdSave it as .claude/skills/oma-coordination/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
oma-coordination
description
Guide for coordinating PM, Frontend, Backend, Mobile, and QA agents on complex projects via CLI. Use for manual step-by-step coordination and workflow guidance.

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
  • resources/examples.md
  • 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. Start with PM task decomposition.
  3. Identify priority tiers and shared contracts.
Scenes
  1. PREPARE: Define session, domains, and task decomposition needs.
  2. ACT: Spawn agents by priority with separate workspaces.
  3. VERIFY: Monitor progress and API/data contract alignment.
  4. FINALIZE: Run QA review and coordinate remediation.
Transitions
  • If task is simple, route to one specialist.
  • If user wants automated execution, use orchestrator.
  • If QA finds CRITICAL issues, re-spawn responsible agents.
Failure and recovery
  • If contracts diverge, pause downstream frontend/mobile work until backend/API contract is reconciled.
  • If agent workspaces conflict, split ownership boundaries.
  • If progress stalls, inspect progress files and reissue focused instructions.
Exit
  • Success: specialist outputs are coordinated and QA-reviewed.
  • Partial success: blocked agents, contract conflicts, or QA failures are explicit.

Logical Operations

Actions
ActionSSL primitiveEvidence
Read request and domainsREADUser prompt and project context
Select agent planSELECTPM decomposition and priority tiers
Spawn agentsCALL_TOOLoma agent:spawn
Monitor progressREADprogress-{agent}.md
Validate contractsVALIDATEAPI/data model alignment
Notify coordination statusNOTIFYFinal coordination summary
Show full SKILL.md (257 more words)Show less
Tools and instruments
  • oma agent:spawn, PM/frontend/backend/mobile/QA agents
  • Memory/progress/result files
  • Serena MCP for exploration and modification when used by specialists
Canonical command path
bash
oma agent:spawn pm "<planning task>" <session-id> -w ./pm
oma agent:spawn backend "<backend task>" <session-id> -w ./backend &
oma agent:spawn frontend "<frontend task>" <session-id> -w ./frontend &
wait
Resource scope
ScopeResource target
LOCAL_FSProgress/result files and workspaces
PROCESSAgent spawn commands
MEMORYSession state and task board
CODEBASEShared contracts and implementation areas
Preconditions
  • Task requires multiple domains.
  • PM decomposition can identify independent priority tiers.
Effects and side effects
  • Spawns or guides multiple agents.
  • Coordinates workspace ownership and QA feedback.
Guardrails
  1. Always start with PM Agent for task decomposition
  2. Spawn independent tasks in parallel (same priority tier)
  3. Define API contracts before frontend/mobile tasks
  4. QA review is always the final step
  5. Assign separate workspaces to avoid file conflicts
  6. Always use Serena MCP tools as the primary method for code exploration and modification
  7. Never skip steps in the workflow — follow each step sequentially without omission
Workflow
Step 1: Plan with PM Agent

PM Agent analyzes requirements, selects tech stack, creates task breakdown with priorities.

Step 2: Spawn Agents by Priority

Spawn agents via CLI:

  1. Use spawn-agent.sh for each task
  2. CLI selection follows agent_cli_mapping in oma-config.yaml
  3. Spawn all same-priority tasks in parallel using background processes
bash
# Example: spawn backend and frontend in parallel
oma agent:spawn backend "task description" session-id -w ./backend &
oma agent:spawn frontend "task description" session-id -w ./frontend &
wait
Step 3: Monitor & Coordinate
  • Use memory read tool to poll progress-{agent}.md files
  • Verify API contracts align between agents
  • Ensure shared data models are consistent
Step 4: QA Review

Spawn QA Agent last to review all deliverables. Address CRITICAL issues by re-spawning agents.

Automated Alternative

For fully automated execution without manual spawning, use the orchestrator skill instead.

References

  • Workflow examples: resources/examples.md

© first-fluke, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in benchmarks/runs/oma/.agents/skills/oma-coordination of first-fluke/oh-my-agent.

  • SKILL.md
  • resources/examples.md

Open the folder on GitHubat commit f65bbc0

Compare with similar skills

Manual Multi-Agent Coordination next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Manual Multi-Agent Coordination compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Manual Multi-Agent Coordination this skillfirst-fluke/oh-my-agent1.3k—~1.4kAutomated safety check: PassMIT
Swarm Parallel Dispatchlangchain-ai/langchain-skills1.3k—~3kAutomated safety check: PassMIT
Agents Project Coordinatorasgeirtj/system_prompts_leaks69k—~2.9kAutomated safety check: PassCC0-1.0
Cursor Orchestratecursor/plugins10k—~1.1kAutomated safety check: PassNone
Launching Agent Teamslexler/skill-factory239—~1.3kAutomated safety check: PassApache-2.0
Team Agent Pipelinezereight/gitlab-mcp2k1 repos~1.5kAutomated safety check: PassMIT

Similar skills

  • Swarm Parallel Dispatch

    langchain-ai/langchain-skills

    Official

    Fans a list of independent items out to subagents in parallel, merges the results back into a table and supports retrying only the rows that failed.

    1.3k GitHub stars~3k tokensUpdated 3 days ago
    Agent WorkflowsAuto-check passed

  • Agents Project Coordinator

    asgeirtj/system_prompts_leaks

    Runs a goal as a project in which the agent coordinates separate agent threads, judging when to split the work, and interviews you first when nothing can be verified.

    69k GitHub stars~2.9k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Cursor Orchestrate

    cursor/plugins

    Official

    Splits a large goal into a tree of parallel Cursor cloud agents, with planners, workers and verifiers coordinated by a script and reporting through structured handoffs.

    10k GitHub stars~1.1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Launching Agent Teams

    lexler/skill-factory

    Plans and launches Claude Code agent teams with distinct roles, right-sized tasks and detailed spawn prompts, and says when subagents or worktrees fit better.

    239 GitHub stars~1.3k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

  • Team Agent Pipeline

    zereight/gitlab-mcp

    Spawns a chosen number of coordinated agents on a shared task list and runs them through plan, requirements, execution, verification and fix stages.

    2k GitHub starsUsed in 1 repo~1.5k tokens
    Agent WorkflowsAuto-check passed

  • Agent Orchestrator

    NeverSight/learn-skills.dev

    Meta-agent skill for orchestrating complex tasks through autonomous sub-agents.

    216 GitHub starsUsed in 1 repo~1.4k tokens
    Agent WorkflowsAuto-check passed

More from first-fluke/oh-my-agent

All 57 skills in this repo

  • OMA Multi-Agent Orchestration

    first-fluke/oh-my-agent

    Decomposes a complex feature into tasks, dispatches parallel specialist agents with durable state, and supervises verification, QA review and retries.

    1.3k GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

  • Oma Video

    first-fluke/oh-my-agent

    Create short, explainer, or recorded-demo videos through the OMA video CLI.

    1.3k GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

  • OMA Multi-Agent Orchestrator

    first-fluke/oh-my-agent

    Splits a complex feature into prioritized tasks, spawns specialist CLI subagents in parallel, tracks them through shared memory and verifies each result.

    1.3k GitHub stars~3.1k tokensUpdated yesterday
    Auto-check passed

  • Architecture Decisions and ADRs

    first-fluke/oh-my-agent

    Evaluates system boundaries and tradeoffs and writes architecture recommendations, option comparisons or ADRs, with a Mermaid diagram when structure changes.

    1.3k GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed

  • OMA Backend Agent

    first-fluke/oh-my-agent

    Backend specialist for APIs, database work, authentication and migrations that follows clean architecture with router, service and repository layers.

    1.3k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

  • oma Bootstrap

    first-fluke/oh-my-agent

    Installs or checks the oma CLI and its runtimes (bun, uv, serena) in a fresh workspace so that oma-* skills can run their commands.

    1.3k GitHub stars~719 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Manual Multi-Agent Coordination

What does Manual Multi-Agent Coordination do?

Guides step-by-step coordination of PM, frontend, backend, mobile and QA agents on a complex project, with priority tiers, contract checks and QA review. This skill guides manual coordination of several specialist agents on a complex project that spans product management, frontend, backend, mobile and QA. It is meant for step-by-step control rather than full automation, and it tells the agent to send simple single-domain tasks to one specialist, quick fixes to normal handling and automated runs to the orchestrator skill.

When should I use Manual Multi-Agent Coordination?

Manual Multi-Agent Coordination fits situations like: building a feature that spans frontend, backend, mobile and QA work; wanting step-by-step control over when each specialist agent starts; keeping API contracts aligned between agents working in parallel.

How do I install Manual Multi-Agent Coordination in Claude Code?

Run `npx skills add first-fluke/oh-my-agent --skill oma-coordination -a claude-code`. Or copy the skill folder (benchmarks/runs/oma/.agents/skills/oma-coordination in first-fluke/oh-my-agent) into .claude/skills/oma-coordination in your project. Claude Code loads it when a task matches its description.

How do I install Manual Multi-Agent Coordination in Codex?

Run `npx skills add first-fluke/oh-my-agent --skill oma-coordination -a codex`. Or copy the skill folder (benchmarks/runs/oma/.agents/skills/oma-coordination in first-fluke/oh-my-agent) into .agents/skills/oma-coordination in your project. Codex loads it when a task matches its description.

Can I use Manual Multi-Agent Coordination in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add first-fluke/oh-my-agent --skill oma-coordination -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/oma-coordination, .gemini/skills/oma-coordination, .github/skills/oma-coordination and .opencode/skills/oma-coordination in your project.

What does Manual Multi-Agent Coordination need to run?

SKILL.md names no scripts, command-line tools or credentials: Manual Multi-Agent Coordination is instructions for the agent only. Our summary lists: The `oma` CLI with its PM, frontend, backend, mobile, QA and orchestrator skills.

Does Manual Multi-Agent Coordination access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Manual Multi-Agent Coordination safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Manual Multi-Agent Coordination use?

Manual Multi-Agent Coordination is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Manual Multi-Agent Coordination use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Manual Multi-Agent Coordination?

Skills that share tags, products or a category with Manual Multi-Agent Coordination: Swarm Parallel Dispatch (langchain-ai/langchain-skills, 1.3k stars), Agents Project Coordinator (asgeirtj/system_prompts_leaks, 69k stars), Cursor Orchestrate (cursor/plugins, 10k stars) and Launching Agent Teams (lexler/skill-factory, 239 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Manual Multi-Agent Coordination?

first-fluke (a GitHub organization) maintains it in first-fluke/oh-my-agent, which has 1,338 GitHub stars. The repository holds 57 skills in this directory. The repository was last updated on October 8, 2026.

Source: first-fluke/oh-my-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.