| name | ctx-handover |
| description | Per-session handover artifact writer. Wraps `ctx handover write` with `--summary` and `--next` (both required, both validated non-placeholder by the CLI). Always invoked as the final step of `/ctx-wrap-up`; not the user-facing trigger. When `.context/kb/` exists, also folds postdated closeouts into the handover and archives them. |
Write a Handover
Capture the session's narrative thread so the next session (a
fresh agent, a different operator, a cold restart the next
morning) can resume without re-deriving context probabilistically
from canonical files plus journal.
This skill is the sole authoritative recall artifact writer
(per KB-RULES.md §Four inviolable rules: "the handover is
the sole authoritative recall artifact"). SESSION_LOG.md
entries, closeouts, and journal entries are mid-flight surfaces;
the handover is what /ctx-remember reads on session start.
Authoritative background reading:
.context/ingest/KB-RULES.md §Four inviolable rules;
specs/kb-editorial-pipeline.md §Interface.
When to Use
/ctx-wrap-up owns the user-facing trigger for session-end
("let's wrap up", "save state", "leave a handover", "before I
go", "stepping away") and delegates to this skill as its final
step. Do not advertise this skill as a direct user trigger.
- Mandatory tail of
/ctx-wrap-up. Every /ctx-wrap-up
run ends with this skill.
- Mid-session checkpoint when the user wants to pause without
consuming closeouts (use
--no-fold). This is the one case
where direct invocation is appropriate.
When NOT to Use
- Nothing meaningful happened (only read files, quick lookup);
but check with the user. A no-op session still benefits from
a "nothing changed; next-step is X" handover when the next
session has zero context.
