jmb-implement-frontier
jmb-implement-frontier [n…]
Launch a batch: one subagent per ticket, each in its worktree with its branch <n>-<slug> and its isolated resources (the "Worktree for ticket <n>" column of Isolated resources in § Worktree), and each takes its ticket to its own PR against main. Orchestrate from the main checkout, on main, and nothing is committed here: every commit is made by a subagent in its worktree.
What is already running belongs to jmb-sync: relaunching the PRs that fell behind, cleaning up the worktrees that landed and summarizing what is waiting. The human chains the two and sets the pace: merge, jmb-sync, and jmb-implement-frontier when they want more work running.
Vocabulary: the frontier is the open tickets with no open blocker and no assignee; the batch, those launched at once; to sync is to merge origin/main into the ticket's branch, and the subagent does it.
What is specific to the project comes from docs/agents/flow.md: each § is one of its headings, and each italic is the label of one of its fields. If the project does not have it, stop and ask for jmb-setup to be run. This skill belongs to parallel mode, which § Worktree turns on: if flow.md does not have it, stop and say that the project's flow is sequential only.
Steps
-
Place.
git branch --show-currentgivesmain,git status --porcelainis empty andgit pull --ff-only origin mainbringsmainup to date. If anything fails, stop and say so. Done whenmainis the head oforigin/mainwith a clean tree. -
The batch. With numbers, it is exactly those: the human sets the cap by listing them, and launching costs quota out of the week in which they will merge. A ticket with an open blocker stays out and you say so; one already assigned to you without a branch goes in without claiming it again (it is a launch that got lost).
Without numbers, the frontier and two by default (
<label>is Label of § Tickets, and it goes in a-ffield because that is howghencodes it: it may contain spaces):