create-handoff

To create a session handoff document, generate a YAML skeleton that captures next steps, blockers, and decisions, then save it to the designated shared handoffs folder using a standardized session-name and date-time stamp convention.

The correct file path for handoff documentation follows the thoughts/shared/handoffs/{session-name}/YYYY-MM-DD_HH-MM_description.yaml structure, enforcing a strict YAML format to ensure consistent traceability across collaborative AI sessions.

You need YAML formatted handoffs because they provide a structured skeleton that preserves essential context, enabling the next agent to quickly resume work by reviewing clear next steps, blockers, and decisions without losing prior session state.

Yes, this handoff approach supports multi-agent coordination by generating concise context transfer documents that enforce consistent session naming, folder placement, and date-time stamping to maintain traceability across different agent sessions.

A YAML handoff skeleton should include fields for next steps, blockers, and decisions, along with proper session naming, folder placement, and date-time stamping to guide the next agent and help them resume work quickly.

The best way to standardize context transfer is to enforce a consistent YAML file path and field guideline structure, ensuring every handoff document follows the same session-name convention and date-time stamping for reliable traceability.