/assemble

The queue-runner. /forge closes one ticket; /assemble closes the spec: it walks the frontier until the queue is empty, giving every ticket the same discipline a solo /forge run would, and refusing to let volume dilute rigor.

Preconditions

1. A queue exists — a spec with open tickets on the tracker docs/agentic-skills/tracker.md pins, tickets readable with their blocking edges. No queue — say so and point at /tickets.
2. The repo config exists — the same grounding /forge reads: stack commands, glossary, ADRs, document set when pinned.

The start gate

Before any code moves, present the plan: the frontier (tickets whose blockers are all closed), the order you will walk it, and which non-blocking tickets could run in parallel. Render this gate through the host's question tool when one exists, recommended option first; otherwise ask the same question as a numbered list. Interactive gates follow ADR 0008. Nothing starts until the plan is accepted; the user can trim the queue or re-order it at this gate.

The loop

For each ticket, in frontier order — the ticket whose blockers are all closed goes first; a ticket blocked by open work is never started early: