session-continuity

To prevent accidental commits, session notes are stored in a dedicated notes home outside the project repository. This read-only approach ensures that session continuity and handoff prompts preserve individual work context without modifying the actual repository.

The best way to handle developer handoffs is to use structured handoff prompts that provide clear guidance and scope boundaries. This prevents scope creep and redundant work by ensuring the incoming developer understands the exact session context and decisions made previously.

You record coding session progress by running the session-end command. This captures your project decisions and work context in personal session notes stored securely outside the project repository, ensuring continuity for future sessions.

Yes, you can maintain session continuity while preserving privacy. Sensitive session notes and personal information flow are managed in a dedicated notes home separate from project repositories, preventing unintended information leaks between projects.

Session management applies directly to coding, collaborative work sessions, and project transitions. It manages session start and end commands, project profiles, and handoff prompts to ensure smooth transitions and preserve individual work context across teams.