# Ticket Ship

> Take a tracker ticket through to shipped: find or start the PR, drive it to mergeable, update the ticket state, draft the stakeholder message. Use for Jira/Linear (or acli) tickets assigned to you.

- Skill: `outthislife/ticket-ship` (Agent Skill)
- Install (CLI): `npx skillmds@latest add outthislife/ticket-ship`
- Raw SKILL.md: https://api.skillmd.com/api/skills/outthislife/ticket-ship/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: outthislife (https://skillmd.com/u/outthislife)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/outthislife/ticket-ship

---


# Ticket → Ship

The ticket-shaped parts of shipping. The PR mechanics live in their own skills —
this is what a tracker adds on top.

## Steps

1. Read the ticket and list the assigned work (`acli`, Jira, Linear, etc.).
2. Confirm the correct base branch(es) before starting — some orgs need a
   release branch plus the default (`stacked-pr`). Never assume; verify the
   org's rule.
3. Find the existing PR or start one (`work` → `pr-update`), then drive it
   mergeable (`pr-ready`) and polish before handoff (`clean`).
4. Move the ticket to the right state (In Review / Test / whatever this tracker
   uses). Link the PR on the ticket.
5. Draft the stakeholder update — Slack or a ticket comment, short, `no-tropes`.
   Don't send it unless asked.

## Don't

- Assume the base branch.
- Mark the ticket done while CI is red or review threads are open.
- Let the ticket and the PR tell different stories about the state of the work.