This guide explains how to use the Handoff Manager after installation. The Handoff Manager provides a structured approach to maintaining context between development sessions through handoff documents and milestones.
After installation (either via the basic or advanced method), you'll have access to the Handoff Manager custom mode in Roo-Code.
To use the Handoff System, first switch to the handoff-manager mode in Roo-Code:
Switch to handoff-manager mode
The Handoff Manager supports these primary operations:
flowchart TD
classDef mainNode fill:#333,stroke:#666,stroke-width:2px,color:#fff,font-size:14px
classDef subNode fill:#444,stroke:#666,stroke-width:1px,color:#fff,font-size:12px
classDef decisionNode fill:#354,stroke:#576,stroke-width:1px,color:#fff,font-size:12px
A[Start] --> B{Choose<br>Operation}
B -->|Create New| C[Create Handoff]
B -->|Consolidate| D[Create Milestone]
B -->|Resume Work| E[Restore Session]
C --> F[Standard Handoff]
C --> G[Handoff with<br>Conversation Extract]
D --> H[Process Existing<br>Handoffs]
D --> I[Generate Summary<br>and Lessons]
E --> J[Load Relevant<br>Context]
E --> K[Resume Project<br>Work]
class A,C,D,E mainNode
class F,G,H,I,J,K subNode
class B decisionNode
A handoff document captures the current state of your project for future reference.
To create a standard handoff document:
I need to create a handoff document for our current work. Please follow the handoff creation workflow.
The Handoff Manager will:
- Examine the handoffs directory to determine the next handoff number
- Create a properly structured handoff document
- Include relevant information from the current session
If you want to include insights from your conversation history:
-
Export your conversation from Roo-Code by clicking the cloud download icon in the task modal:
Click the cloud download icon (highlighted above) to download your conversation history.
-
Save the downloaded file (any filename is fine)
-
Either:
- Place the exported conversation file in the
handoffs/0-system/chat-history/
directory, or - Provide a direct path to the file when requesting a handoff
- Place the exported conversation file in the
-
Use this prompt:
I need to create a handoff document incorporating insights from our conversation.
The Handoff Manager will:
- Find the conversation file (either in the chat-history directory or at the specified path)
- Execute the appropriate extraction script
- Analyze the conversation for key insights
- Create an enhanced handoff that includes these insights
When you've accumulated 3-5 handoffs or completed a significant project phase, create a milestone:
I need to create a milestone document for our completed work. Please follow the milestone creation workflow.
The Handoff Manager will:
- Check if you have handoff documents in the root directory
- Calculate the next milestone number
- Create a milestone directory
- Move relevant handoff files into the milestone directory
- Generate two key documents:
0-milestone-summary.md
: High-level overview of achievements0-lessons-learned.md
: Reusable patterns and solutions
When returning to a project after a break, use the session restoration feature:
I need to restore context from our previous work. Please follow the session restoration workflow.
The Handoff Manager will:
- Examine the handoffs directory structure
- Identify the most relevant documents to load
- Read milestone summaries and recent handoffs
- Provide a comprehensive understanding of the project's current state
Handoff documents follow this structure:
# [TOPIC] Handoff - [DATE]
## Summary
[2-3 sentence overview]
## Priority Development Requirements (PDR)
- **HIGH**: [Must address immediately]
- **MEDIUM**: [Address soon]
- **LOW**: [Be aware]
## Discoveries
- [Unexpected finding 1]
- [Unexpected finding 2]
## Problems & Solutions
- **Problem**: [Issue description]
**Solution**: [Solution applied]
```code example if needed```
## Work in Progress
- [Task 1]: [Progress %]
- [Task 2]: [Progress %]
## Deviations
- [Changed X to Y because Z]
## References
- [doc/path1]
- [doc/path2]
Milestone directories contain these key files:
# [Project/Feature] Milestone Summary - [DATE]
## Changes Implemented
- [Major change 1]
- [Major change 2]
- [Major change 3]
## Key Decisions
- [Decision 1]: [Rationale]
- [Decision 2]: [Rationale]
- [Decision 3]: [Rationale]
## Discoveries
- [Important finding 1]
- [Important finding 2]
- [Important finding 3]
## Current System State
- [Component 1]: [Status]
- [Component 2]: [Status]
- [Component 3]: [Status]
# Lessons Learned - [Feature/Component]
## [Problem Category 1]
**Problem:** [Issue description]
**Solution:**
- [Solution step 1]
- [Solution step 2]
- [Solution step 3]
## [Problem Category 2]
**Problem:** [Issue description]
**Solution:**
- [Implementation details]
- [Code patterns to use]
- [Testing approach]
## Tools and Libraries
- [Tool/Library 1]: [Usage and value]
- [Tool/Library 2]: [Usage and value]
## Edge Cases
- [Edge case 1]: [Handling approach]
- [Edge case 2]: [Handling approach]
The conversation extraction feature enhances handoffs with insights from your conversation history:
-
Find the Task Modal:
- Look for the task modal in the top-right corner of your Roo-Code interface
- It shows information about your current session including tokens, context window, and cache
-
Locate and Click the Download Button:
- Click the cloud download button (highlighted above) to download your conversation history
- The file size is displayed next to the button (e.g., 2.87 MB)
-
Save the Conversation File:
- Choose a location on your computer to save the file
- You can use any filename you prefer
- The file will be saved in Markdown format
Once you have exported your conversation, you have two options:
-
Automatic Detection:
- Place the exported file in the
handoffs/0-system/chat-history/
directory - The Handoff Manager will automatically find and use this file
- Place the exported file in the
-
Manual Specification:
- Keep the file anywhere on your system
- When running the extraction script manually, provide the file path:
node handoffs/0-system/scripts/1-extract-conversation.js /path/to/your/conversation-file.md
-
Create Enhanced Handoff:
- Simply request a handoff with conversation extraction:
I need to create a handoff document incorporating insights from our conversation.
- The Handoff Manager will automatically find the conversation file and process it
- Simply request a handoff with conversation extraction:
Create handoff documents when:
- Context becomes ~30% irrelevant to current task
- After completing significant project segments
- After 10+ conversation exchanges
- During debugging sessions exceeding 5 exchanges without resolution
Create milestone documents when:
- Completing major features or components
- After 3-5 handoffs accumulate
- A significant project phase concludes
- Critical bug is fixed
- Implementation approach has changed
For effective knowledge transfer:
- Be Specific: Include concrete details and measurable outcomes
- Focus on Changes: Emphasize what's different now vs. before
- Highlight Roadblocks: Document issues encountered and their solutions
- Track Progress: Note completion percentages for in-progress items
- Reference Related Files: Link to relevant code or documentation
For more targeted handoffs:
I need to create a handoff document focused on [SPECIFIC TOPIC]. Please include these key points:
- [KEY POINT 1]
- [KEY POINT 2]
- [KEY POINT 3]
For organizing handoff files when creating milestones, the system provides automation scripts:
- JavaScript:
handoffs/0-system/scripts/2-create-milestone.js
- Python:
handoffs/0-system/scripts/2-create-milestone.py
These scripts create the milestone directory and move relevant handoff files.
Keep your handoffs directory organized:
- Handoff documents in root directory:
handoffs/1-setup.md
- Milestone directories:
handoffs/1-core-entities/
- System files in 0-prefixed directories:
handoffs/0-instructions/
- Conversation exports in:
handoffs/0-system/chat-history/
If extraction scripts fail:
- Check that you have Python or Node.js installed
- Verify the conversation file exists and is properly formatted
- Check script permissions
- Try the alternative script (Python or JavaScript)
- Make sure the file is in the expected location, or provide a full path to the file
If the Handoff Manager can't find expected directories:
- Verify the handoffs directory exists at the project root
- Check if the 0-instructions and 0-system directories exist
- Ensure you are in handoff-manager mode
- Verify file permissions allow creation and modification
If the handoff-manager mode isn't working correctly:
- Check that the .roomodes file contains the handoff-manager mode
- Verify the file pattern regex is correct
- Restart Roo-Code to load the updated configuration