handoverlisted

# Handover — Drop the Spec, Don't Push It You wrote a spec in this thinker session. The orchestrator (a separate session on this machine) needs it. The simplest reliable transfer: validate the header, copy the file into the shared inbox, done. **This is the user's commit moment** — when they invoke handover, they're deciding "build this." There is no second gate on the orchestrator side; don't add one. Read `DO-IT.md` for the shared protocol (lanes, numbering, header fields). This skill just does the drop. ## When this is the wrong skill If the spec hasn't been written yet, stop — go back to `think`. Handover moves a *finished* spec; it doesn't write one. ## Protocol ### Step 1 — Validate the header (fail here, not at build time) The spec must carry this header. **Refuse to drop and tell the user what's missing if any required field is absent or empty:** ``` topic: one line intent: 1-2 plain sentences — what success MEANS and WHY (REQUIRED, non-empty; this is the why, distinct from acceptance) source_brief: NNN | none code_snapshot: <git sha the spec was audited against> acceptance: N criteria, N > 0 (REQUIRED) target_paths: files/dirs in scope supersedes: NNN | none # set only on a resubmission after a bounce ignore: e.g. "the rejected-alternatives section is context, not a requirement" ``` Hard checks (these are the whole reason handover validates instead of the orchestrator discovering it later): - `intent:`