The Build Loop — From Idea to Committed Code
Handoffs: Continuity Between Sessions
A Session Is Not a Project
Context windows end. The toolkit writes a handoff at the close of /do, /run-todo, /run-tests, /todo and /end, stored per session and per branch under docs/.output/handoffs/{YYYY-MM}/. Path resolution goes through handoff-path.js, so two branches never overwrite each other's handoff.
node .claude/core/handoff-path.js latest # where is the newest handoff?
/prime reads the latest handoff plus recent git history to rebuild your context at the start of the next session.
Evidence Beats Intent
A handoff is a record of earlier intent. When it disagrees with the repository, the current files and git state win. Check the branch and status, then treat the handoff as a lead to follow, not an order to obey.
Do not trust "not deployed yet" or "tests passing" lines in an inherited handoff. Re-verify against the real command output before building on them.
An inherited handoff says a migration was never applied, but `git log` and the schema show it was. What do you trust?