agent-handoff-packager

Capturing agent state and decisions for handoff involves inventorying read or edited files, documenting rationale, and emitting a single artifact. This structured package ensures the next agent can resume the task without losing prior context or open questions.

The best way to save a checkpoint is to package context, diffs, and open questions into a deterministic handoff artifact. This approach captures the exact working state, allowing a future agent or session to resume seamlessly without re-establishing prior context.

You need to create a portable handoff artifact when transferring work between agents, saving a session checkpoint, or resuming work in a new conversation. It specifies the required structure to ensure the next agent seamlessly continues the task.

The agent handoff packager operates with no external dependencies, using standard agent session data to build the handoff artifact. It inventories edited files and captures decisions to ensure the handoff package is self-contained and portable.

Yes, you can and should document open questions and blockers when packaging agent state. The handoff artifact explicitly captures key decisions, rationale, and blockers to guide the next agent in resolving outstanding issues during session resumption.