close-outlisted

# /close-out — Ordered wave merge and lifecycle cleanup **Type:** lifecycle / merge orchestration ## Purpose After all `/work-issue` loops for a planned wave set have completed (or a subset is ready), `close-out` merges the resulting PRs in **wave order**: wave 1 first, then wave 2 (rebased onto the wave 1 merge), then wave 3, and so on. This preserves the execution order that `/plan-issues` established and prevents PRs from stepping on each other at merge time. ### Pipeline position ``` plan-issues → work-issue (wave 1) → work-issue (wave 2) → ... → close-out ``` ## Invocation variants ``` /close-out --repo owner/slug /close-out --repo owner/slug --wave 1 # close out only wave 1 /close-out --repo owner/slug --wave 1,2 # close out waves 1 and 2 in order /close-out # → resolves repo from cwd, closes all open waves ``` ## Design constraint: no GitHub Projects dependency `close-out` tracks all state through standard GitHub primitives only: - **Issue state:** open / closed via `gh issue view` and `gh issue close` - **Wave labels:** `wave:<n>` (set by `/plan-issues`) on issues and their PRs - **PR state:** open / merged / closed via `gh pr list` and `gh pr merge` No `gh project` CLI calls. No board columns. No project fields. Works in any repo regardless of whether GitHub Projects is enabled. ## Workflow ### 1. Wave discovery Find all waves with work ready to merge: ```bash gh issue list --repo <slug> --state open