session-handoff

To preserve workflow context when pausing a session, you can generate a handoff artifact that captures active phases, completed steps, decisions, blockers, and next actions. This prevents work loss by writing a loadable file at the project root.

The best way to resume an in-progress workflow across team members is using a context handoff file. It captures the in-progress state and next actions, allowing a new agent to load the exact session context and continue safely without losing prior decisions.

A session handoff checkpoint prevents loss of work at phase boundaries by automatically capturing the active phase and in-progress state. It writes this context to a project root file, ensuring seamless resumption when the workflow transfers across sessions.

Yes, you can transfer active session context without losing blockers and decisions. The handoff process explicitly records completed steps, ongoing decisions, and current blockers into a dedicated markdown file for the next agent to load.

No specific dependencies are required to create a context checkpoint for resuming work later. The process operates independently to capture your session state and write a standard markdown handoff file directly at your project root.

Your workflow loses progress without a checkpoint because the active phase, in-progress steps, and decisions are not captured. Writing a dedicated handoff file ensures the next agent loads the full context and resumes safely.