claude-ship-workflow

CSW takes a ticket from your tracker to a merged pull request, then cleans up after itself. Superpowers owns how the work gets done. CSW owns how it gets shipped and closed out.

This is one person's idiosyncratic workflow, and it is probably not yours. It assumes worktrees, merge commits, conventional commits, a review step that a human actually performs, and a tracker that holds the brief. It is MIT-licensed and public because the shape is reusable even when the details are not. Fork it, or lift the parts you want.

The three phases

Prep is the optional pass in front of the dispatch. It reads the ticket, brainstorms it for the questions that would stop an unattended run, and then answers the ones it can defend an answer to — anything with a precedent in the codebase, a convention the repo follows, or a cheap reversal becomes a recorded decision with its reasoning rather than a question. The test is mechanical: if prep can mark an option "(Recommended)", it has its answer. What survives is put to you in the run, in one round — and usually that is nothing.