wrap-up-ritual

To write a developer handoff note, signal a session wrap-up and the tool generates a structured note with Completed, Pending, Learned, and Context sections, saving it to .claude/handoff.md for immediate continuity.

Capturing learned insights during a session wrap-up involves recording what was done, what remains, and key takeaways. The tool extracts durable learnings to MEMORY.md while overwriting the previous handoff note to prevent stale context.

This session wrap-up tool works for both exploratory work and code-heavy development. It triggers whenever you signal a wrap-up, handoff, or done for today, including cases involving decisions, fixes, or unresolved test failures.

To prevent stale progress capture files, the tool overwrites the previous handoff note in .claude/handoff.md instead of creating new files. This ensures only the latest state is saved without accumulating outdated notes.

You can use this knowledge management skill to prepare context for a different developer. It produces stranger-ready handoffs containing specific file paths, decision rationale, and actionable next steps rather than vague summaries.

You should not use a structured handoff note if your workflow requires a permanent historical log of every session, because this tool overwrites the previous handoff file to maintain only the single most recent state.