phase-done

name	phase-done
description	Closes a tracker issue: verifies the work is genuinely done (exit criteria, gates, docs, changelog), writes the close narrative into the PR description, ensures the PR declares `Closes #N`, posts the handoff comment, and deletes the implemented plan file. Use when the user says a work item is complete or asks to close it out.
allowed-tools	["Read","Edit","Grep","Glob","Bash"]
argument-hint	[issue number] (optional)

/phase-done

The closing step of the issue workflow (CLAUDE.md). Only run this once the issue's work is actually finished — this skill verifies and records, it does not decide the work is done on your behalf.

Steps

1. Identify the issue being closed (the user names it, or it is the issue this branch's PR declares Closes #N for). Read it with gh issue view <n> --comments; if it links a plan file (docs/plans/*.md), that file's ## Exit criteria also applies.
2. Verify every ## Exit criteria checkbox is ticked — in the issue body and in any linked plan file. If any remain - [ ], stop and list them — do not tick a criterion yourself just to proceed; a tick must reflect real, verified state (e.g. "workspace builds" means someone actually ran cargo build --workspace and it succeeded). Tick verified boxes in the issue body via gh issue edit <n> --body-file. 2a. Relationships check (scripts/gh-rel.sh tree <n>; .claude/rules/issue-relationships.md): if the issue is a parent with open sub-issues, do NOT close it — finish or re-parent the children first (a parent's job is done only when its decomposition is). Closing this issue auto-unblocks anything it was blocking, which is expected; note any dependents that become workable so the handoff comment can point at them.
3. Spec-adherence check: for work that shipped spec-facing behaviour, confirm a conformance pass happened (/spec-audit findings addressed or filed as new issues). If it never happened, stop and say so — that is an unmet exit criterion in spirit. 3a. CNF zero-drift gate: confirm a full CNF 2.0 run (/run-conformance → scripts/conformance.sh) happened at close and shows zero drift vs the committed baseline (docs/conformance/ehrbase-rs/results.json + verdicts.json; the baseline only ratchets upward), and that the ratcheted docs/conformance/ehrbase-rs/ artifacts (results.json, verdicts.json, CONFORMANCE_REPORT/STATEMENT/CERTIFICATE.md, badge*.json) are in-branch. No green CNF run → the issue is not closable. 3b. User docs + changelog updated? If this work changed a user-visible surface (REST, configuration, CLI, deployment artifacts), confirm BOTH: the matching website/book/src page was updated in-branch (and scripts/assemble-oas.sh re-run if the REST contract changed — .claude/rules/docs-website.md), AND a CHANGELOG.md [Unreleased] entry exists (.claude/rules/changelog.md; CI changelog-guard enforces it). If not, stop: both are part of the deliverable. 3c. Living-reference-doc maintenance: confirm the living reference docs (docs/architecture.md, docs/VERSIONS.md) were refreshed to verified reality for anything this work changed. (There is no blueprint/design-doc layer — internal plan/design files are deleted in the PR that implements them; the durable record is the closed issues + PR descriptions, CHANGELOG.md, git history, and these living reference docs.)
4. Write the close narrative into the PR description: what shipped, the key decisions with their spec citations, the gate results, and what was deliberately left out (with follow-up issue numbers). The PR description + the issue thread ARE the build record (there is no PROGRESS.md — retired 2026-07-20).
5. Post the handoff comment on the issue (gh issue comment <n>): where things stand at close, what was deliberately left out (with the follow-up issue numbers), and what a follow-up session should do first.
6. Ensure the PR body declares Closes #<n> (gh pr view / gh pr edit) so the merge into develop auto-closes the issue — never close the issue by hand when a PR carries the work.
7. Delete the implemented plan file in the same PR (the delete-on-implementation lifecycle; docs/plans/README.md) — unless another still-open issue consumes the same plan file; then note that on the issue instead. Exceptions that are NEVER deleted: docs/plans/WORKLIST.md (the tracker pointer stub), docs/plans/README.md (the lifecycle guide), and docs/conformance/cnf-design.md (the permanent CNF 2.0 design record, owner ruling 2026-07-22).
8. Remind the user to commit the close on the current conventional-type branch (feat/… etc., per the CLAUDE.md branch hard rule).

What this skill does not do

It does not run cargo build, the test suite, or the CNF pipeline to "check" the exit criteria for you — those must already have been run and have genuinely passed before this skill is invoked. If in doubt, run /run-conformance or the relevant cargo command first.