create_handoff

Create a handoff document by capturing your current task context, references, changes made, and next steps into a structured YAML file saved under thoughts/shared/handoffs. The document includes session metadata, timestamps, and organized sections for task summaries, artifacts, and learnings to enable seamless continuation by another agent.

A handoff file includes task descriptions, relevant file references, a summary of changes and decisions made, key learnings, post-mortem insights, generated artifacts, and prioritized next steps. Frontmatter contains session name, timestamps, and Braintrust IDs to maintain full context across agent transitions.

Generate a handoff during session transitions, when handing off work to another agent, or upon task completion. Handoffs are essential when an active ledger exists for your continuity stream, ensuring incoming agents have complete project context without repeating work.

Yes. Handoffs automate documentation by deriving session names from your active ledger, generating YAML metadata automatically, and structuring content into predefined sections. This reduces manual effort while ensuring consistent, thorough documentation for cross-session transfers.

Handoff documents are concise, session-specific transfers designed for agent-to-agent continuity, with structured sections and machine-readable frontmatter. General documentation is broader; handoffs focus on immediate next steps, recent decisions, and artifacts needed to resume work without context loss.

Yes. Handoffs enrich metadata with repository info, timestamps, and file references to ground the work in its source context. This ensures the receiving agent can locate relevant files and understand the project state at the moment of handoff.