The situation
You stop midway through a change. Tomorrow, neither you nor a fresh agent can easily tell which idea was tested, which files changed, or whether the next step is safe to take.
The idea in one paragraph
Resumable work leaves a small written handoff at a useful stopping point. It does not try to preserve every thought. It records the outcome being pursued, the current state, evidence already gathered, the next bounded step, and any risk that must be checked before continuing.
| At a pause | Write down | Why it matters |
|---|---|---|
| Goal | What success means | Prevents a new direction |
| State | What changed | Gives a starting point |
| Proof | What was checked | Avoids false certainty |
| Next step | One small action | Makes restarting easier |
How it actually works
A handoff can live in a project note, task record, or other agreed project file. The exact location matters less than being easy to find and current. A later session reads it alongside the actual files and checks whether reality still matches the note. Written state is a guide, not a substitute for looking.
What this changes for you
- Stop after a testable slice rather than in the middle of a broad rewrite.
- End each session with a plain-language handoff.
- Name unverified assumptions instead of presenting them as completed work.
Where it breaks
A handoff becomes misleading when it is copied forward without checking it. Too much detail is also hard to scan; too little forces rediscovery. If a change has external consequences, record its status clearly and verify before repeating it.
Terms used on this page
Handoff: A short record that helps another session continue work.
Bounded step: A small action with a clear result and limit.
Verification: Checking evidence that a claimed result is true.
Read next
Continue to Automatic checks.