handoff-execute

# /handoff-execute Receive a handoff brief in a fresh agent session and execute it end-to-end with a source-ingestion gate before planning, source-cited plan steps, acceptance-verified output, and a ground-truth retro. This is the receiving-side counterpart to `/handoff` — `/handoff` writes the brief, `/handoff-execute` enforces the discipline that turns the brief into ground-truth work. > **Structured execution spec:** [`protocol.yon`](protocol.yon). Read it for the canonical rules and step sequence; this file is explanation. The two must stay in sync — if you edit one, update the other and refresh the `@STAMP` date. ## Boundary Use `handoff-execute` to consume a handoff brief produced by `/handoff` (YAML frontmatter `type: handoff` + YON body blocks). Do not use it for: - `PLAN.md` or `implementation_plan.md` — use `/plan-execute` (different schema, no `@SOURCES` block, no retro requirement). - A formal post-execution self-gate — use `/verify` (requires intent/plan/execution artifacts; checks for drift). - Independent outside-agent review of completed work — use `/cold-review` (reviews, doesn't execute). - Re-verifying one specific claim — use `/double-check`. `handoff-execute` is the only skill that consumes a handoff brief and produces the canonical retro file. ## Invocation ``` /handoff-execute "<absolute-path-to-brief>" ``` The brief path is required. Always quote the path — Windows vault paths may contain spaces. **Force flag** — `/handoff-execute --force "<p...