dev-ship

A standing ship authorization. Use when you say "ship it", "ship this", "execute and ship", or "ship it to main" about work planned or discussed in the current session — that is the full no-reconfirmation authorization. ALSO use on a generic go-word ("execute it", "do it", "do it now", "let's go", "go ahead", "run it") about a code-change plan discussed in session whose natural endpoint is shipping — but then follow the Triggers section: confirm scope before merging. It means — execute the agreed plan in a worktree, test and validate everything locally, and if confident there is no regression risk, open a PR and merge it (the merge is the deploy trigger). NOT for go-words about non-shipping work (sending messages, running scripts, drafting), and NOT for product release flows that have their own process and authorization (app-store submissions, OTA releases, package/CLI/plugin version bumps — each a separate authorization).