oma-coordination

1# Multi-Agent Workflow Guide
2 
3## Scheduling
4 
5### Goal
6Guide manual multi-agent coordination for complex work that spans PM, frontend, backend, mobile, and QA responsibilities.
7 
8### Intent signature
9- User wants step-by-step coordination, manual agent spawning, or multi-domain work planning without full automation.
10- Task spans multiple specialist agents and requires contract alignment.
11 
12### When to use
13 
14- Complex feature spanning multiple domains (full-stack, mobile)
15- Coordination needed between frontend, backend, mobile, and QA
16- User wants step-by-step guidance for multi-agent coordination
17 
18### When NOT to use
19 
20- Simple single-domain task -> use the specific agent directly
21- User wants automated execution -> use orchestrator
22- Quick bug fixes or minor changes
23 
24### Expected inputs
25- Complex feature or project goal
26- Required domains and priority tiers
27- Workspace/session constraints and API/data contract needs
28 
29### Expected outputs
30- Manual coordination sequence
31- PM task decomposition, agent spawn order, monitoring guidance, and QA review step
32- API/data contract alignment checkpoints
33 
34### Dependencies
35- PM, frontend, backend, mobile, QA, and orchestrator skills
36- CLI `oma agent spawn` and progress/result memory conventions
37 
38### Control-flow features
39- Branches by task complexity, priority tiers, dependency ordering, and whether automation is desired
40- Spawns independent same-priority tasks in parallel when appropriate
41- Monitors progress files and contract alignment
42…