develop-batch
Develop Batch — Parallel Roadmap Fan-out Orchestrator
Extends single-item /develop-next across the whole conflict-free frontier. One
invocation = the next batch of dependency-ready, write-disjoint roadmap items taken from
"outstanding" to "merged + ticked": developed in parallel in separate git worktrees,
then merged serially. Everything per-item (branching, review, develop, QA loop,
finalise, and the merge gate / roadmap tick) is delegated unchanged to the existing
pipelines and reuses develop-next's merge machinery — this skill only adds the
fan-out and the serial finalize lane on top.
The whole strategy in one line: develop in parallel, merge serially.
Policy baseline (inherited from develop-next, user-ratified): auto-merge everything
green; auto-answer routine pipeline questions with the recommended option and log them;
stop at manual items, planning gaps, and any hard HALT. The one axis develop-next does
not consider — write-conflict between concurrent items — is decided here by the
--batch selector's touches: analysis, never by eye.