next-laneslisted

Choose the next lanes, propose them, and dispatch them once the user approves. **This body is self-sufficient — run it without reading anything else.** The pointers name where an argument or a piece of evidence lives, for when a step surprises you: the evidence under every rule here is [`docs/research/choosing-what-to-dispatch-next.md`](../../../docs/research/choosing-what-to-dispatch-next.md) and, for what a week of running it measured against what actually merged, [`docs/research/lane-scheduling-starvation-and-shared-state.md`](../../../docs/research/lane-scheduling-starvation-and-shared-state.md). The standing policy is `docs/agents/workflow.md` → *How a batch is chosen* and, for what independence means, → *A batch is independent in git, and coupled through the platform*. The tracker's is `docs/agents/issue-tracker.md`, and the labels are `docs/agents/triage-labels.md` → *The roster*. **This skill destroys nothing.** It reads the board and it opens lanes. It never removes a worktree, never closes one out and never writes to the tracker. Closing a lane out belongs to `/review-pr`, and removing one belongs to a person. **Propose, then wait.** It never dispatches without approval. ## The ceiling is policy, not a derived number **Three lanes, unless the user says otherwise.** Say so plainly when you report, because the number is a starting value rather than a truth: **no published source recommends a number of concurrent agents.** Orca states none and says agents choose t