oma-coordination

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