session-wrap

To prevent context loss after an AI session restart, execute an end-of-session protocol that captures learnings, updates next steps in a scratchpad, and verifies uncommitted changes. This structured wrap-up ensures state persistence and maintains session continuity across interactions.

The best way to manage uncommitted changes before ending a development session is to run a structured wrap-up protocol that performs git status checks, identifies pending modifications, and prompts for necessary updates to documentation to secure your workflow state.

To persist AI workflow state and plan next steps across coding sessions, append identified key learnings to a patterns file and update a scratchpad with actionable items. This state persistence approach bridges context gaps between consecutive interactions.

Session state persistence relies on automated git integration checks rather than manual verification. The wrap-up protocol automatically executes git status checks to verify uncommitted changes, ensuring no work is lost before context compaction or session termination occurs.

You should use an end-of-session protocol for knowledge capture when concluding any AI coding interaction that generated new learnings or uncommitted changes. It is essential for workflow automation when you need to preserve state continuity and store patterns for future reference.

AI productivity drops after restarting a session due to context loss and missing state persistence. Using a scratchpad to store actionable next steps and capturing learnings in a patterns file maintains knowledge continuity, preventing the AI from losing track of previous workflow states.