Session Continuity
Session continuity leverages the established session workflow to maintain context between conversations through systematic reference and documentation patterns.
Guidelines
Effective continuity enables seamless project progression across multiple sessions by preserving context, decisions, and momentum through structured documentation and reference strategies.
Cross-Session References
Start new sessions by referencing previous work:
Please read the conversation log from yesterday’s session about project optimization and continue from where we left off.
The memory system automatically loads:
- Previous session outcomes and decisions
- Identified next steps and follow-up work
- Project state and file modifications
- Methodology refinements and insights
Context Loading
Load relevant context through multiple channels:
- Memory system for profile and methodology consistency
- File system for current project state
- Conversation logs for previous session outcomes
- Diary entries for insights and alternative approaches
Tag-Based Discovery
Conversation logs and diary entries use consistent tagging for cross-reference capability and searchable context recovery:
**Tags:** `#domain-topic` `#activity-type` `#outcome-result`The three-part tag structure provides systematic organization:
- Domain-topic (
#infrastructure-optimization,#development-debugging) - Subject area and specific focus - Activity-type (
#troubleshooting,#planning,#implementation) - Type of work performed - Outcome-result (
#completed,#blocked,#insights-gained) - Session result or status
Usage Examples
Reference previous work using tag patterns:
Find all conversation logs tagged with #infrastructure-optimization to review previous optimization approaches.
Search diary entries with #troubleshooting tags for insights about debugging methodologies used in past sessions.
Matching tags between conversation logs and diary entries creates cross-reference capability, enabling comprehensive context recovery from both factual records and reflective insights.
Project Workflows
Long-term projects benefit from systematic handoff patterns between sessions that preserve progress and maintain momentum.
Session Handoffs
Between sessions, project state is maintained through:
- File modifications preserved in the repository
- Progress documentation in conversation logs
- Next steps identification for future sessions
- Context preservation through structured notes
Workflow Example
Multi-session projects demonstrate how systematic handoffs maintain progress and context across conversation boundaries.
Session One
- Review
/Users/username/github/charts/helm-chart/values.yaml - Identify optimization opportunities
- Document findings in conversation log
Session Two
- Read previous conversation log
- Continue optimization work on
values.yaml - Implement identified improvements
- Update documentation
Best Practices
Effective continuity requires consistent application of documentation and reference patterns.
Documentation Discipline
- Create conversation logs for significant sessions
- Generate diary entries for reflection and insights
- Use consistent tagging for searchability
- Maintain clear next steps identification
Context Management
- Reference previous logs when starting new sessions
- Load relevant files before beginning work
- Verify profile consistency across sessions
- Maintain project directory organization
Progress Tracking
- Document incremental progress in logs
- Identify blocking issues for future resolution
- Track methodology refinements over time
- Build competency through repeated application