handoverlisted

# Handover First capture, then continue: ensure the durable harvest is current, then emit the transient continuation the next agent starts from. Guiding principle: existing durable artifacts should already provide suitable context for handover. This skill is to **improve token efficiency** with transient guidance those durable artifacts elide — and to confirm they are in good condition. ## Harvest first — always, both branches Before emitting anything, confirm the capture pass is current: - **Governing slice:** its `## Harvest` must be fresh — the `fresh-as-of` stamp matches the current lifecycle position (phase / stage + head commit). If stale, run `/harvest` first — do not re-survey what the harvest already swept. - **Another governing artifact (RFC, spec, review …):** the capture pass still runs — route produced / learned / open to their sinks per `harvest.md` §5; orientation falls back to entity queries. Phase status accurate and work committed (or its uncommitted state noted) remain adjacent truth checks. ## The dial One skill, two weights: - **light** — print a continuation prompt; nothing written. - **full** — write the `handover.md` context packet and print instructions pointing at it. Default by context: phase boundary, dispatch conclude, or complex in-flight state → full; a simple "continue this in a fresh context" → light. The user's explicit ask overrides. ## Light: the continuation prompt Print: ``` /route (path to the governing artifact an