handoff

To preserve context when ending a Claude session, generate a structured handoff document that captures decisions, progress, and code changes. This creates a Markdown file with sections like Current State, What We Did, and Next Steps for easy continuity.

The best way to maintain session continuity when switching projects is to write a structured Markdown handoff file. This file documents open questions, code changes, and context to remember, allowing the next session to resume work without re-explaining.

Create a structured handoff document for project breaks by triggering the handoff process. It automatically writes a Markdown file to .claude/handoffs/ with the current date and description, detailing what you did, decisions made, and next steps.

Session handoff documentation does not require external dependencies. It operates independently to generate a Markdown file containing structured sections for current state, code changes, context to remember, and next steps to ensure workflow continuity.

A Markdown session handoff file includes structured sections for Current State, What We Did, Decisions Made, Code Changes, Open Questions, Context to Remember, and Next Steps. This ensures future work starts with the correct background and constraints.