finishedlisted

# Session closure Write down what the next session would otherwise have to rediscover. The record is only useful if it is honest: a log that reports intentions as accomplishments costs more than no log, because the next session trusts it. ## 0. Defer to the repository first `Glob` for `.codex/prompts/*finish*.md`, `.codex/prompts/*wrap*.md`, and the same patterns under `.claude/commands/` — they catch variants such as `finished.md` or `wrap-up.md`. If one matches, `Read` it, follow its instructions instead of the steps below, and say which file you used. Otherwise continue here. ## 1. Learn the project's conventions Read `AGENTS.md` and `CLAUDE.md` for the stated handoff or logging convention, then locate the artifacts the project actually keeps: `HANDOFF.md`, `CODEX_HANDOFF.md`, `STATUS.md`, `SESSION_LOG.md`, `NOTES.md`, or a dated `logs/` directory. Match the structure already in the file. If the project keeps none, summarize in the reply and ask **once** whether to start a durable file — do not create one unprompted. ## 2. Establish what changed ``` git status --short git log --oneline <session-start>..HEAD git diff --stat ``` Ground every claim in one of these outputs. For each item, classify it: - **Done and verified** — the change exists and a check passed. Name the check. - **Done, unverified** — the change exists; nothing confirmed it works. - **Half-finished** — started, and the next session needs to know where the seam is. - **Decided, not implemented** — a