agent toolingby first-fluke
Multi-Agent Workflow Guide
first-fluke/oma-coordination
Guide for coordinating PM, Frontend, Backend, Mobile, and QA agents on complex projects via CLI.
What it changes
Passed 21 of 21 test cases with the skill, and 9 of 21 without it.
Without skill41%
With skill100%
Checks it passed that the model alone missed
- Employs oma agent:spawn CLI syntax for launching sub-agents.
- Recommends Serena MCP tools for code exploration and modification tasks.
- Directs checking agent status in progress-{agent}[-{sessionId}].md files.
and 16 more in the full report
13 fixed9 passed either way0 still failing0 broke
- Pass-rate lift
- +59 pp
- Tokens
- +17%
- Agent turns
- 0%
- Response time
- -50%
Model gemini-3.6-flashMeasured 8/27/2026v422 of 22 cases passed with skill · 21 comparable
See it in action
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
PromptWhen specialist agents need to inspect project structure, edit files, or perform code symbol searches, which tool suite should they rely on?
What was checked, without and with the skill| Checked | Without skill | With skill |
|---|
| Specifies Serena MCP tools as the primary method for code exploration and modification. | Missed | Passed |
|---|
What's inside
The instructions your model reads when the skill loads.
SKILL.md161 linessingle file
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
Track record
Benchmark
21 / 21
test cases passed, vs 9 / 21 without
Adoption
- Users
- 0
- Times used
- 0
Safety and source details
SkillSafety
✓ 3 of 3 passed✓Code scan15 of 15 checks clean
0 critical · 0 warning · 0 info — scanner v5 — 8/25/2026
View 15 scanner checks
live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing
✓IntentSafe
LLM judge · does the skill do what it claims
✓ContentClean
LLM judge · policy & harmful-content review
Source
Importedfirst-fluke / oh-my-agent
.agents/skills/oma-coordination/SKILL.md
License MITImported 8/25/2026Version v4