shiplisted

# ship — land verified work Shipping is a claim to the rest of the team: *this is done, here's the proof, here's why*. This skill assembles that claim from the Spine instead of from memory. ## Steps 1. **Read the Spine.** Load `journal.md` (acceptance criteria + the latest verification result), `conventions.md` (test/build commands and any VCS or PR conventions), `context.md` (shared language), and `decisions/` (ADRs to cite). 2. **Gate on verify.** Confirm every acceptance criterion is met *with evidence* in `journal.md`. If anything is unverified or failing, stop and run `verify` first — do not ship unproven work. 3. **Prepare the branch.** If you're on the default branch, create a feature branch first. Make sure the working tree is clean and the diff is only what this work intends to ship. 4. **Commit hygiene.** Group changes into clear, conventional commits with messages that explain *why*, following any pattern in `conventions.md`. 5. **Compose the PR body from the Spine.** Summary of what changed and why; the acceptance criteria as a ticked checklist; links to the ADRs that justify the approach; and the verification evidence (the real command output, not a claim). Name things using the Spine's shared language. 6. **Push and open the PR** against the base branch. Run the test/build commands from `conventions.md` one last time if CI won't. 7. **Record in the Spine.** Update `journal.md`: mark the work shipped, link the PR, and set *N