Android Agent Orchestration (android-agent-orchestration)

Coordinate complex Android (and companion backend) engineering across parallel sub-agents without file collisions, device contention, or unverified merges. Pairs a tool-agnostic orchestration workflow with dedicated command references for Orca, OpenSpec, and AgentMemory.

When to Use

• Coordinating multi-module Android features, Component Gallery/theme setup, Gradle foundation work, or companion backend services across sub-agents
• Operating in Manual Mode (active user review for UI/UX changes, deployment notifications) vs. Automatic Mode (40-min inactivity fallback, 20-sec user opt-in pause during auto tests)
• Running the Coordinator Cycle Workflow (sweep, check progress and merge, run the cycle, /cycle) to drain inbox messages, inspect workers, validate mobile/backend tasks, merge cleanly, run host smoke tests, and execute complete cleanup
• Naming, spawning, and managing isolated git-worktree sub-agents
• Assigning scarce physical or virtual (AVD) test devices from a pool to sub-agents and testing rebased branches on device
• Performing Coordinator verification, triaging bugs (fix on the spot vs. send back to the original sub-agent), and cleaning up worktrees and sub-agents after merge

1. Phase 0: Pre-Flight Environment, Long-Lived Cache & Device Pool Check

1.1 Long-Lived Coordinator Local Cache (~/.config/android-skill-derek/)

As Coordinator, maintain a persistent local cache in ~/.config/android-skill-derek/ (config.json, devices.json, and cache/) with a long retention window across runs: