phase-completelisted

# Phase Complete ## Purpose A "phase" is a labeled chunk of multi-step work — typically the unit that ends with a release tag, a milestone, or an explicit hand-off to a different team. This skill verifies the exit criteria of the phase before the lead declares it done. Distinct from per-task verification (`verify-agent-work`) — phase-complete looks at the phase as a whole. ## Scope Operates on a phase definition (typically captured in `decisions.md` or `plan.md`). Reads the current state of tasks, hooks, and artifacts. Read-only; produces a go/no-go signal. NOT in scope: actually closing the phase. The lead does that based on this skill's output and any judgment calls. ## Automated pass 1. Read the phase's exit criteria from `plan.md` or `decisions.md`. If criteria aren't documented, surface "phase has no documented exit criteria" and stop — phase completion isn't testable without them. 2. For each criterion, verify: - **Tasks.** Every task assigned to the phase is `completed`. Any "in_progress" or "blocked" tasks block phase-complete. - **Hooks.** No outstanding `BLOCK`-severity hook entries since the phase started. - **Bypasses.** No active hook bypasses (any open bypass is a debt to clear before phase close). - **Decisions.** `decisions.md` has been updated since the most recent task activity. A stale `decisions.md` at phase end means the audit trail is incomplete. - **Tests.** The full test suite passes (delegate to