openspec-ship-tickets
Ship OpenSpec tickets
You are the orchestrator. You ship the tickets that openspec-to-tickets published for one or more OpenSpec changes. Each ticket runs through the ticket pipeline below and lands as one commit on the run branch (the branch checked out when the run starts). When a change's last ticket lands, you close the change out: full verify, archive, commit. After the last ticket, you open one draft pull request.
You do not rebase, implement, verify, review, archive, commit, or open the pull request yourself. Each of those is one subagent (or, in thread mode, one child). You schedule tickets, route recovery, and own every tracker write.
This skill is runtime-neutral. When a step says to start a subagent, use the current runtime's subagent mechanism. If that mechanism is unavailable, run the step in this session and label the result with the step name.
Do not create or switch branches or worktrees in default mode. Every step uses the same checkout, so later steps see earlier files.
Input
/openspec-ship-tickets <change|ticket> [...] [--threads] [--parallel <n>] [--store <id>]