handover
Produce a high-detail continuation/handover file so a fresh session can resume with absolute accuracy. Use at every clean task close, when all todos are green-gated, and ALWAYS before a context compac
SKILL.md.claude/skills/handover/SKILL.md
GitHubHandover / continuation file
Produce a single Markdown file that lets a brand-new session (zero prior context) continue THIS work with no loss of fidelity. This is Req 6 of the Kingdom operating contract (knowledge/global/operating-contract.md).
When to produce one (any of)
- A task or planned run closed clean and green-gated.
- All todos are complete.
- Context is getting heavy — produce it BEFORE a compact, not after. Watch the window and keep ~15–20% in reserve to write this file faithfully. A compact that happens before the handover exists is a continuity failure.
- The owner asks (
/handover).
Where it goes (keep the existing naming — do NOT invent a new scheme)
- Kingdom control-plane work (this repo, ~/kingdom):
docs/<project-slug-or-area>/kingdom-continuation-<ISO8601>.mdISO8601 =YYYY-MM-DDTHH-MM-SS(hyphens, local time, matching the existing series). - Inside a tracked project (~/kingdom/projects/<slug>): that project's own
continuation location and name (e.g.
docs/<project>-continuation-<ISO8601>.md). - The new file SUPERSEDES the prior one — add a
supersedes:line in the frontmatter and state "where this conflicts with an older note, this wins."
Required sections (omit none; write "none" if empty)
- Frontmatter — title, version (the ISO8601), supersedes, repo(s), branch, state.
- Git state (verify before trusting) — current branch, last-known
main/branch tip SHA, what is squash-merged vs local-only, any divergence traps. SHAs are "last observed" — include the exact commands to re-verify (do not assert as fact). - What CLOSED this run — merged/landed work, with the files touched.
- OPEN workstreams (carried forward) — each with: current status, the decision pending (if any), the next concrete step, and any owner-gated blocker.
- Known untracked / in-flight files — anything dirty on the tree that is expected.
- Verification commands — copy-paste block to run at next session start (git state, gates, build) with the expected output for each.
- Standing rules & gotchas — the environment/policy traps that bit this run (cross-reference knowledge/policies/ rather than re-deriving them).
- Next action — the single first thing the next session should do.
Method
- Reconstruct git truth FIRST:
git log --oneline -5,git status -sb,git branch --show-current, and (for projects)git log origin/main— never assert a SHA you have not just observed. - Pull forward the still-open items from the PRIOR continuation file (don't drop them).
- Write the file. Stage ONLY that file (
git add <path>; nevergit add -Aon a dirty tree). Commit in isolation, then it is safe to/clearor allow compact. - If this is also a planned-run close, follow knowledge/policies/run-close.md (push Kingdom + ensure draft PR) after the file is committed.
Token discipline (Req 1)
Dense and pointer-based. Reference file paths and policy docs instead of pasting large bodies. The goal is total reconstructability per token, not length.