forward

Automating session handoff creates a structured markdown document with session context and automatically enters plan mode to define the next workflow step. It ensures continuity by generating actionable follow-ups for the next session.

Wrapping up a git workflow session involves generating a handoff markdown file in a designated inbox path and triggering plan-mode preparation. This automatically outlines the scope and next steps for the subsequent session.

Plan-mode initiation works by automatically transitioning into a planning phase after the handoff document is written. It guides the generation of a subsequent plan file that references the handoff and defines the next session's scope.

Yes, you can use markdown to structure session planning and handoff documentation. The process writes handoff files to a specific inbox path using a timestamped markdown format, ensuring session context and outcomes are recorded.

No external dependencies are required to trigger automatic session handoff and planning. The workflow operates independently to write the handoff file and initiate plan mode for the next session.

You should not use an automated handoff workflow if your session requires continuous, uninterrupted execution without distinct breaks. It is designed for discrete sessions needing structured context preservation and explicit next-step planning.