wrap-up-ritual

Session handoff notes are generated by detecting wrap-up signals and writing a structured summary of completed work, pending tasks, and learnings. This creates a single overwriting handoff file so the next developer can resume immediately.

Saving session context is best handled by a structured wrap-up process that detects explicit and implicit ending signals. It captures the session state into a three-part summary file, ensuring no context is lost before the session terminates.

Knowledge capture works by enforcing a three-part structure that records completed work, pending tasks, and learned insights. It then writes these details to a handoff file and promotes permanent learnings to a memory file for future sessions.

Implicit signal triggering is supported alongside explicit commands like "wrap up" or "save progress." The system detects natural session-ending phrases to automatically generate the handoff file and capture memory without requiring specific syntax.

This session management approach overwrites previous handoff notes to maintain a single current state. By writing an overwriting handoff file, it ensures the next developer reads only the latest context without sorting through historical session logs.