Session Close-Out (/done)

Goal: everything a handoff protects — durable state, skill training, a clean environment — without producing a resume prompt. This exists because "a prompt for the next session already exists" is NOT the same as "the session was closed out properly": the Skills Review, the learnings sweep, and the record-writing were routinely getting skipped whenever the prompt happened to be pre-generated. /done makes those non-optional regardless of how the next session gets started.

Relationship to handoff

This skill IS the handoff skill minus one step. Read the handoff SKILL.md and execute its sequence with one modification:

• Run steps 1–7 and 9 exactly as written there: land the in-flight unit, sweep loose ends, write the handoff record, refresh the atlas vault note, shut down what you started, git end-of-work sweep, Skills Review, per-skill learnings sweep, archive the session (last action).
• SKIP step 8 (post the resume handoff) entirely. Do not write a resume brief, do not post a resume chip, do not produce a copyable resume prompt in a code block, regardless of which surface the user is on (this install's brief directory and resume surfaces: LOCAL.md beside this skill, when your copy keeps one, Resume step skipped). If a continuation prompt already exists, leave it alone — do not regenerate, improve, or duplicate it.

All of handoff's discipline still applies verbatim — write-through during the session, reconcile-with-reality before writing the record, concurrent-session rails, trustworthy-claim standards, and the failure modes list. /done changes what you emit at the end, not the rigor of anything before it.

Remaining work

Work left on the table does not resurrect step 8. Instead:

• Record it where the next session will actually look: the follow-ups tracker, the queue file (if this is queue work), and the handoff record's "exact next action" line. The record must still pass the handoff test — a fresh session could resume from it — even though no prompt points at it.
• If the pre-existing continuation prompt is now WRONG (the session changed the plan, the branch, or the blocker it names), say so explicitly in the record and tell the user in the final message that the old prompt is stale — but the fix is the user regenerating via /handoff, not /done quietly emitting a new one.

The final message

End with a short close-out summary: what landed (with PR/commit refs), the Skills Review verdicts, any learnings appended, and confirmation the environment is down and the session is archived. No code-block prompt, no chip.

Related skills

• status-update: a close-out covering several units may carry a dashboard; it never replaces the record.

Capturing learnings

Close-out lessons share mechanics with handoff — append them to LEARNINGS.md beside the handoff skill, when your copy keeps one (tagged /done where the distinction matters) rather than growing a parallel journal here.