core practice · coding
Create a durable agent handoff
Implement createHandoff(input) returning a JSON-safe object with schemaVersion 1, goal, status, completed, evidence, blockers, and nextAction. Reject an input that claims status 'complete' without evidence. nextAction must be one concrete action, not a list, and every evidence item must include both command and observed output.
The mechanism
A context window is a worker shift, not durable storage. The repository or workflow log owns the recoverable state: what was requested, what changed, what was verified, what failed, and the smallest safe next action. A handoff is correct when a fresh process can resume from artifacts alone.
Expected evidence
A checkpoint that a fresh session can validate and resume without reading prior chat.
Try this drill in the practice workspace →
Hints when you need them
- Persist observations, not merely 'tests passed'.
- A good next action is the smallest safe continuation from the recorded state.
Watch for these mistakes
- Saving a narrative summary without exact files, commands, or observed results
- Marking a task complete without durable verification evidence
- Letting the chat transcript become the only record of decisions and remaining work