What problem does it solve? Running multiple AI agents in parallel on one repository fails in predictable ways: two lanes fight over the single physical TV, a shared git stash stack hands one lane another lane's work, worktrees get cut from the wrong base, and full cross-builds fill the disk. This Skill decides, before any worker launches, whether a fleet is worth it and how to partition it safely. ## Core Features & Use Cases - Fleet go/no-go decision: A checklist for when fanning out pays (disjoint files, independent compilation, host-verifiable work) versus doing it yourself. - TV lane assignment: At most one lane gets the physical television; all others verify on the simulator with their own SIM_DIR. - Worktree and disk hygiene: Cut each worktree from a named base, seed gitignored files like src/config.local.h, keep build trees outside the worktree, and run make check only. - Worker-prompt block: A paste-ready rules block covering base verification, device access, disk limits, and the no-stash rule, since workflow agents cannot be reached mid-run. - Use Case: You want three agents to work on separate UI modules of a webOS app at once. Use this Skill to cut three worktrees from origin/main, assign the TV to none of them, and paste the worker-prompt block into each lane. ## Quick Start Ask the agent to plan a parallel fleet for this repo, splitting the work into independent lanes with one lane allowed to use the television.