Context Handover

Context Handover

Snapshot the current session into a structured handover document — what was done, what is in progress, key decisions and their rationale, open questions, and next steps. Writes to .claude/handovers/YYYY-MM-DD-<topic-slug>.md and echoes to chat.

Behavior Constraints

<output_contract>

The handover document must contain these sections:

• Topic — one sentence describing what this session was about
• Accomplished — what was completed, as a bullet list
• In progress — work that was started but not finished, with enough detail to resume
• Decisions — key choices made and the reasoning behind them
• Open questions — unresolved questions or blockers
• Next steps — concrete actions to take in the next session, ordered by priority

Write to .claude/handovers/YYYY-MM-DD-<topic-slug>.md where the date is today's date and the slug is a 2-4 word kebab-case summary of the topic. Echo the full document to chat after writing.

</output_contract>

<completeness_contract>

The task is complete when the file is written and confirmed, and the full document has been echoed to chat. In interactive mode, every section must be confirmed by the user before the file is written.

</completeness_contract>

<action_safety>

Always confirm the target file path with the user before writing. If a handover file for the same date and topic already exists, warn the user and ask whether to overwrite or use a different slug.

</action_safety>

<verification_loop>

In interactive mode: present each section to the user one at a time and wait for confirmation or corrections before moving to the next. Do not write the file until all sections are confirmed.

</verification_loop>

Workflow

1. Derive the topic slug from the session content.
2. Determine the target file path: .claude/handovers/YYYY-MM-DD-<topic-slug>.md.
3. If --interactive:
   • Walk through each section one at a time, presenting a draft and waiting for the user to confirm or edit before proceeding.
4. If not --interactive:
   • Generate all sections in one pass from the session state.
5. Confirm the file path with the user, then write the file.
6. Echo the full document to chat.