Agent skill · Testing & QA

oma-coordination

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.

first-flukegithub.com/first-flukeGitHub ↗
claude-codecodexcursorMIT
Install
npx skills add first-fluke/oh-my-agent --skill oma-coordination --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: .agents/skills/oma-coordination/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,204
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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` an

What's inside
Steps it walks through
  1. Scheduling
  2. Goal
  3. Intent signature
  4. When to use
  5. When NOT to use
  6. Expected inputs
  7. Expected outputs
  8. Dependencies
  9. Control-flow features
  10. Structural Flow
  11. Entry
  12. Scenes
  13. Transitions
  14. Failure and recovery
Commands it runs
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
oma agent:spawn backend "task description" session-id -w ./backend &
oma agent:spawn frontend "task description" session-id -w ./frontend &
More from oh-my-agent
All skills →
oma-orchestratorAutomated multi-agent orchestrator that spawns CLI subagents in parallel, coordinates via MCP…AI & Agentsoma-slideHTML presentation deck generator and multi-format exporter. Generates distinctive, animation-rich…Design & Presentationoma-hwpConvert HWP / HWPX / HWPML files to Markdown using kordoc. Extracts text, headings, tables, lists…Data & Analyticsoma-mobileMobile specialist for Flutter, React Native, and Swift native iOS development. Use for mobile app…Frontendoma-backendBackend specialist for APIs, databases, authentication with clean architecture…Securityoma-videoShort-form, explainer, and demo video generation via a key-optional 3-tier router. Composes…Data & Analytics
About this skill
What does the oma-coordination skill do?

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.

How do I install it?

Run `npx skills add first-fluke/oh-my-agent --skill oma-coordination --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From first-fluke/oh-my-agent, a repository with 1,204 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.