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. Under `/work-issue`'s default `merge_policy: defer`, this skill is **the merge point**: loops deliberately end at an open PR with the `ready-for-close-out` verdict, and close-out performs the ordered merge, the issue close, the label/branch cleanup, and the one deploy per run. Field semantics: `skills/work-issue/SKILL.md`, section "Merge policy (`merge_policy`)". ### 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 ``` **`--wave`** takes a comma-separated list of wave numbers. It is validated against the wave labels that actually exist in the repo, and it never changes the merge order: waves are always processed in ascending numeric order regardless of the or