fleet-handing-off

To generate a handoff doc, provide a brief focus for the next session and request the AI to summarize done work, in-flight tasks, blockers, and next steps, referencing commits, files, PRs, and ADRs for context replay.

A handoff document should include completed work, in-flight tasks, blockers, and next steps. It must also reference commits, files, PRs, and ADRs to enable rapid context replay and suggest next-session skills for the incoming agent.

You need to create a context-preservation summary when a session is ending or a different agent and stage is taking over, compacting the current conversation to reduce rework and ensure smooth transitions.

Yes, the handoff doc explicitly references commits, files, PRs, and ADRs. This enables the next agent to rapidly replay context and understand prior decisions without manually searching through history.

No, generating a handoff doc requires no external dependencies or components. You simply provide a brief focus for the next session, and the AI compacts the current conversation into a structured summary.

The best way to summarize done work and blockers is to generate a focused handoff doc that lists these items alongside in-flight tasks and next steps, ensuring the fresh agent can pick up the work immediately.