ueagentWhat you will have
A reviewed handoff connected to the current code state, with an explicit next action for the receiving agent.
Step by step
Record the current state
Update the task handoff with the goal, acceptance criteria, completed work, pending work, decisions, changed files, test results, and known issues. Use concrete paths and commands so the next session can verify the record.
Save a recovery checkpoint
Save terminal context and the structured handoff before leaving a session. Checkpoints preserve recovery material; they do not roll back your repository or reconstruct a model's private conversation. Save code separately through your usual Git workflow.
Inspect the repository before continuing
Stop the old session before switching agents. Review the working directory, branch, commit, and changed files in the handoff checks. If code has changed since a verification run, rerun the relevant checks instead of treating the old result as current.
Review and pass on the handoff
Choose the receiving agent and inspect the prepared handoff text. Correct outdated steps or missing evidence before sending it through the terminal. Confirm the next action explicitly; preparing a handoff does not automatically submit a command.
Check before you continue
- Record the next action and unresolved issues, including failed checks.
- Confirm directory, branch, commit, and uncommitted changes.
- Review the handoff text and rerun stale verification before proceeding.
Questions about this workflow
Does a checkpoint restore the source code?
No. A recovery checkpoint stores terminal context and handoff material. Repository changes require your normal Git or file recovery process; inspect them before continuing.
Can a handoff transfer private conversations between models?
No. A handoff is an explicit record you prepare and review. It provides context to the next agent without converting another CLI's private conversation history.