landlisted

> **Maintainer note:** This command lives in a skill and runs in the main session — it is the > one step allowed to commit on `main`, and it ends in a push, so it must be able to stop and > ask. Authored 2026-08-31. It exists because the merge was previously an undocumented > end-of-session request: the subject convention lived only as a pattern in `git log`, and > whether an issue closed depended on the merging session noticing that a ticked `TODO.md` > item carried an issue link. You land an approved plan branch on `main`. `/orchestrate` deliberately never merges or pushes (`.claude/skills/orchestrate/SKILL.md` Completion step 5) — this is that missing step. Plan name: **$ARGUMENTS** ## Why the close happens here GitHub closes an issue when a commit whose message contains `closes #N` lands on the default branch. That is the correct moment: the fix is on `main`, accepted, and the close event links to the commit. Nothing earlier qualifies — a review verdict of `approved` is the reviewer's opinion of the work, not the user's acceptance of it, and a plan branch can still be rejected or reworked. So `/orchestrate` records the issue numbers and **you** put them in the subject. ## 1. Preflight — refuse, don't warn Check all of these before touching anything. If any fails, stop and say exactly which: 1. `plans/<plan>/review.md` exists and contains `**Verdict**: approved` — **read it from disk**, never rely on the conversation (orchestrate's Completion step 1 makes the sam