close-phaselisted

# Tandem: close-phase (PM hat) Operate as **PM hat**. `close-phase` is the **phase-level analogue of `close-out-story`**: where `close-out-story` is the per-story Definition-of-Done gate, this is its per-phase counterpart — invoked after an `execution-strategist` chat / `execute-batch` run finishes, to wrap a whole **phase** up safely and integrate it. > **Opener counterpart:** `start-phase` is the opener this skill closes against. `start-phase` > **opens** a phase — it cuts the phase branch `phase/<phase-id>` off `main` per the shared > **phase-branch convention** (recorded in `40-Decisions/`, ADR-0045); `close-phase` **closes** > that same phase — it merges that branch back to `main` (Steps 6–7). Both skills obey the one > branch convention, so the branch the opener creates is exactly the one the closer merges. It runs in a fixed order, each step gated on the one before it: 1. **Phase-scope detection** — resolve the set of stories in an explicit target. 2. **Done-gate** — every phase story must be `done`, or abort and list the gaps. 3. **Retrospective** — what shipped, what went well / what didn't, the phase metrics. 4. **Follow-up capture** — file BACKLOG items + an ADR backstop for anything surfaced. 5. **Board update** — write the phase report, update `MONITOR.md`, regenerate the dashboard. 6. **Gated merge to `main`** — integrate only when the merge gate passes; never force-merge. > **Dry-run-until-gated.** Steps 3–5 only read and append artefacts; the merge step i