gs-openspec-ship
Ship OpenSpec changes
You are the orchestrator. You do not rebase, implement, verify, review, archive, commit, or open the pull request yourself. Rebase the current branch onto the remote's default branch once. Then for each change, run the seven steps below in order, revisiting affected steps when recovery invalidates their results. Each step is one subagent. Wait for it to finish before you start the next. After the last change, open one draft pull request for the commits this run made, unless the batch stopped with unfinished edits.
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.
The run is already in the checkout where the work belongs. Do not create or switch branches or worktrees. Every step uses that same checkout, so later steps see earlier files.
Changes run one at a time. Finish or block a change before you start the next.
Input
/gs-openspec-ship <change> [<change> ...]
Also accept a prose list, including "implement the following openspec change(s):" followed by change names.
An optional --store <id> applies to every OpenSpec command in the run. Pass it through. When the user names no store, tell each OpenSpec subagent that no store was named so it follows the store rules in the skill it is reading.