Running a Batch
Take a batch from ready rows to closed plans, one thread per plan.
In prs mode, use this order to take a batch from TODO rows to closed plans. The plans skill owns the sequence.
Read the Frontier
Type /plans. You see ready rows and what blocks the rest. Pick a ready row for a thread. Run one thread at a time per checkout, since its row stays DOING while it works.
Start a Plan
Type /plans do <id> in a fresh thread. The agent cuts the plan's branch from the trunk or the REVIEW layer it stacks on. Stacking on a REVIEW layer waits until no open layer below holds an unresolved thread a reviewer started. The agent implements the plan and opens its PR or stack layer.
Wait for Hand Back
Keep the same thread. It babysits the layer's whole stack, bottom first, in the drive mode of the Babysit playbook, through the reviewer round until every layer reaches handoff. Handoff needs every layer's checks passing and no conflict with its base. Its rows go to REVIEW when it stops. A row whose PR it could not get green goes to BLOCKED instead, with the failing check or conflict as its note. Only at handoff does the reply name ready plans that stack on this layer. Start each in a new thread.
Handle a Later Review
If a review lands outside a babysit, type /plans review <id>. You get a fix round on the owning branch. The agent rebases every owned layer above onto the fix and pushes those layers with a lease.
Merge Bottom First
Merge the PRs yourself, bottom first. The skill never merges. At the next /plans do, a merged blocker releases its dependents even if its row still reads REVIEW.
Close Merged Plans
Type /plans close <id> for each merged plan. It stamps the plan's landed draft with the merge commit, sets the row DONE, and settles the thread where the harness supports it.
Or type /plans close with no id to close each merged plan whose thread has finished. It reports the ones it cannot close yet, such as a plan whose thread is still babysitting. It also removes each closed plan's /tmp/plans-<id>/ scratch once no thread still uses it, and lists the checkouts the plans merged from. A plan in review whose PR now conflicts, usually because a sibling merged first, gets /plans review <id> sent to its own thread, once per head commit. skills plans sweep <Project> --dry-run shows what it would close and remove without writing anything.
Hands-off mode keeps the same order, with every publishing step left to you.