tickets-to-lanes
Tickets to Lanes
human-only. Start this only when a human asks for it by name. It plans how many sessions to spend on a map, and its handoffs are what let those sessions push, wait and stack on each other's unmerged work. A skill chaining into it would be deciding both on the human's behalf. If you arrived here from anywhere but a human naming it, stop.
One /implement-unattended session builds one round and hands back one PR. This skill plans several at once over one map. It splits the map's open build tickets into lanes (one session, one integration branch and one PR each), turns every blocker that crosses lanes into a named handoff, opens one GitHub issue where the lanes coordinate, and hands back a prompt per lane.
The output is prompts. The human pastes each one into a fresh session, and the lanes start there. This session reads the map, writes the issue, and stops.
Each lane runs under the unattended modes' in a lane section (implement-unattended/unattended.md). That section lets a lane push at the handoffs it gives, wait on the handoffs it takes, and stack those onto its integration branch. This skill decides which handoffs exist, and the issue names them, together with the human who started the lanes and the date.
Process
1. Settle the inputs
You need the map, the repo and the target lane count. Take them from the arguments or this session; the repo defaults to the current one. Ask for whatever is missing, the map first. Ask for the lane count in step 3, once the backlog can back a recommendation.
Done when: you have one map number and one owner/name.