tritonkit-device-subagent-orchestration

What problem does it solve? Coordinating multiple AI subagents across TritonKit device-support workstreams risks overlapping write surfaces, conflicting changes, and premature completion claims. This Skill routes work to the correct track plan, assigns scoped subagents, and enforces integration and verification discipline. ## Core Features & Use Cases - Track Routing: Selects exactly one track—Android Emulator support or cross-platform real-device support—and loads the matching space plans as source of truth. - Agent Split and Batching: Maps work to dedicated Codex agent configs (contract, device, app lifecycle, smoke/evidence, build) with ordered batches that respect dependency stabilization. - Write-Surface Isolation: Ensures no two subagents own the same implementation files in a batch, with the main agent owning integration, verification, docs, and completion judgment. - Use Case: When starting Android Emulator support work, spawn the Contract and Fake ADB agents first, then Device and App agents after contract surfaces stabilize, pulling results in batches with focused tests after each. ## Quick Start Ask the agent to orchestrate the TritonKit Android Emulator support track by spawning the scoped subagents defined in the space plan.