ship-issuelisted

# /ship-issue — autonomous ticket delivery Take **one or more issues / stories (`#<issue>`..)** from open all the way to a **reviewed, CI-green pull request** on the base branch, autonomously — using an isolated git worktree and a board of specialist subagents. Merging is gated by `MERGE_MODE` (see Config): by default the run stops with the PR open for a human to merge; set `MERGE_MODE=auto` for fully hands-off delivery. Input (**$ARGUMENTS**): whitespace-delimited tokens. The first one or more tokens are issue / story numbers (`<issue>` below); the token `--` separates issues from extra guidance (everything after `--` is guidance, may be empty). If no `--` is present, every token that looks like a number is treated as an issue number, and the rest as guidance. --- ## Config (defaults — override only if the repo clearly needs it) - `BASE_BRANCH` = the repo's default branch (`gh repo view --json defaultBranchRef -q .defaultBranchRef.name`). - `MERGE_STRATEGY` = `--squash --delete-branch` - `MERGE_MODE` = `manual` — `manual`: stop after the acceptance board with a green, reviewed PR open for a human to merge. `auto`: squash-merge automatically once every gate passes. Start with `manual`; opt into `auto` only in a repo where unattended merges to the base branch are acceptable. - `MAX_FIX_ROUNDS` = `3` (acceptance→fix→re-acceptance loops before escalating to the user) - `WORKTREE_DIR` = a sibling of the repo root: `../<repo>--issue-<first-issue>` (single issue) or `..