Lite is free. Pro adds the quality layer on top.
Hand offbetween sessions.
A few lines at the end of a session save the first ten minutes of the next one.
// the steps
Six steps
01 Write what is doneList what works now, in plain words. Include what you checked, so it is not rechecked.
02 Write what is openList what remains, in order. The first item is where the next session starts.
03 Write what you decidedRecord choices and the reason in a line, especially the ones you rejected, so they are not proposed again.
04 Note the trapsAnything that surprised you: a flaky test, a file that looks safe to delete and is not, a setting that must stay.
05 Save it in the projectPut the note in a file in the repository. A note in a chat is gone with the chat.
06 Start the next session from itOpen with "read the handoff and tell me the first step". Correct any misreading before work begins.
// with adams
Where Adams fits
The handoff written for youProPro writes the handoff from what happened in the session, saves it in the project, and reads it back at the start of the next session.
// faq
Questions
How long should a handoff be?
Ten to twenty lines. If it is longer, it is a document, not a handoff.
Should I commit it?
Usually yes, so it travels with the repository. Keep private notes out of public repositories.
What is the difference from CLAUDE.md?
CLAUDE.md holds standing rules. A handoff holds the state of the current work and is replaced often.
// related