shiplisted

# Ship Deliver end to end: $ARGUMENTS Read `.claude/project-profile.md` first. If it is missing, stop and point at `/project-setup`. This pipeline ends in a deploy, and a deploy driven by a guessed configuration is not something to attempt. ## Stages Each stage is the corresponding skill's job. Follow those files rather than duplicating their rules here, and do not skip a stage because the change looks small: the pipeline is the point, and small changes are exactly the ones that ship broken. ### 0. Plan List what will change: files, data, migrations, tests. For anything touching three or more files or any schema, think the approach through before writing code. Show the plan and get a go-ahead when the change is substantial. For a small fix, state the plan in two lines and continue. ### 1. Implement, see `dev` Read the surrounding code, match its conventions, handle the unhappy paths. If the approach turns out to be wrong mid-implementation, **stop and re-plan**. Pushing through an approach you have stopped believing in produces the changes that are hardest to review and hardest to undo. ### 2. Validate, see `test` Run the profile's required checks. Fix what fails and re-run. Do not continue with a failing required check, and do not reclassify a failure as unrelated to get past it. ### 3. Self-review, see `review` Review your own diff as if someone else wrote it. Fix critical and high findings before continuing. List medium and low findings in the final report ra