Handoff Skill — Development skill for Claude Code

handoff

**Context that survives `/clear`.** A skill for [Claude Code](https://claude.com/claude-code): the next session — an agent with zero context — starts working in 30 seconds instead of re-reading your codebase.

  

A handoff is **not a session log**. It is an executable brief: a living header edited in place on every update, with an append-only log at the bottom that the reader may ignore.

flowchart LR
    A[Session running] -->|"/clear, /compact,
stage done, context full"| B[WRITE]
    B --> C[["handoff.md
survives the reset"]]
    C --> D[RECEIVE]
    D -->|"verify predicates
against reality"| E{Match?}
    E -->|drift| F[Fix, note it]
    E -->|broken premise| G[Report, ask]
    F --> H[First action]
    G --> H
    H -->|"what was missing
goes back into the file"| C

The loop is the point: every receive writes back what the handoff lacked, so the next one is better.

What a handoff looks like

---
status: in progress
summary: parser v2 — migrating the tokenizer
updated: 2026-08-01
---
# Parser v2

**Plan:** .claude/specs/parser.md — stage 3/5, next task 3.2

## Continue work
**First action:** run `pytest -k parser` — 2 tests fail, fix `src/parser.py`
**DoD:** the `[DoD]` predicate below returns `0 failed`

## Map
- `src/parser.py` — anchor `def parse_v2`, the migration target

## Do not do
- Rewriting the lexer — tried, breaks the incremental path

## Expected state of the world
- `git rev-parse --abbrev-ref HEAD` → `feat/parser-v2`
- `[DoD]` `pytest -k parser -q` → now `2 failed` (expected — that's the work)

The receiver runs those predicates before touching anything. Deterministic verification, not vibes.

Why each part exists

Mechanism	Problem it solves
**Publicit