finish-phaselisted

# finish-phase Close out an exec-plan cleanly. The single most-referenced harness ritual: it's what keeps the harness honest about *what's done* and *what's still in flight*. ## When to use - A milestone / sprint / W-phase / feature ships - An exec-plan in `docs/exec-plans/active/` is no longer being worked on - You feel the urge to delete the active plan file (don't — graduate it) ## When NOT to use - The work isn't actually done — finish the work first - The repo has no harness yet — run `/bootstrap-harness` first - The plan was abandoned, not completed — just `mv` it to `docs/exec-plans/abandoned/` (no synthesis needed) --- ## Why this exists (the vibe-coding tie-in) Industry surveys show teams spend **20-30% of sprint capacity** fixing bugs that trace back to vibe-coded work where *nobody wrote down what was actually done*. The pattern is consistent: code ships, no closing note is written, three months later the next change breaks because the original constraints are forgotten. GitHub's 2,500-repo AGENTS.md study found that the single most-queried piece of context an agent asks for is **"what's the current state of this work?"** — and the single most-rotted artifact is the planning doc that was never closed out. Finish-phase forces 60 seconds of synthesis at the right moment. --- ## Workflow — 5 steps ### Step 1 — Discover active plans ```bash ls docs/exec-plans/active/*.md 2>/dev/null ``` If empty: tell the user there's nothing to finish; suggest running `