wrap

To create a session wrap-up summary for multiple projects, use a project-aware cleanup tool that detects touched project directories, updates task trackers like todo.md, and writes per-project handoff timestamps. It synchronizes tasks and lessons across all projects touched during your session.

Capturing project lessons and decisions consistently requires appending meaningful learnings to tasks/lessons.md and recording significant decisions to docs/decisions.md. Cross-project learnings are promoted to a global memory store to prevent lost context and maintain project hygiene.

Updating markdown task trackers involves selectively editing tasks/todo.md to mark completed items, add new ones, and move blocked work into a clearly labeled section with reasons. This ensures your task tracking remains accurate when a session ends.

Yes, session wrap-up conditionally skips file rewrites when nothing changed in the project state. This operational safeguard prevents unnecessary modifications to your task trackers and lessons files during multi-project edits.

You can check for uncommitted work and stray directories before ending a coding session by running a wrap-up process that warns about uncommitted changes and scans for stray directories in your home folder before writing final session timestamps.

You need to promote cross-project learnings to a global memory store when broadly reusable lessons are identified during a session. This avoids duplicates and project-specific implementation details while preserving significant context for future workflows.