subagent-batch-implementationlisted

# subagent-batch-implementation For an **authorized ticket range** where dependencies matter. Flat fan-out (`parallel-subagent-implementation`) assumes independence; this skill assumes a **dependency graph** and delivers it in waves. Its route table decides between the two — come here only once you know the graph is real. A stage parent is a separately launched top-level session. Stage-parent sessions run serially across the GitHub Project; only workers inside an explicitly authorized stage fan out, one level deep. A worker dispatches nothing of its own — every brief says so — and the parent holds every gate and external write. ## Step 0 — Authority and scope Restate the authorization back to the user before starting: > Batch authorized: <owner>/<repo>#201..#208. Commit: yes. Push: <yes/no>. I will stop the batch on the first wave that fails its parent gate. If push authority is unclear, assume **no push** and hand off instead. ## Step 1 — Build the wave plan Read every ticket in the range. Extract `Blocked-by`. Then group into waves: ``` Wave 1: tickets with no unmet blockers Wave 2: tickets unblocked once Wave 1 is Done Wave 3: ... ``` Print the wave plan **before implementing**: ``` Wave 1: #201 (domain service), #202 (API authz) [disjoint lanes] Wave 2: #203 (mobile surface) [blocked by 201, 202] Wave 3: #204..206 [blocked by 203] ``` Rules: - A ticket never enters a wave before its blockers are **Done** (n