Plan Mode: Think First
Plan mode is where you and Sixth figure out what you’re trying to build and how you’ll build it. In this mode, Sixth:- Can read your entire codebase to understand the context
- Won’t make any changes to your files
- Focuses on understanding requirements and creating a strategy
- Helps identify potential issues before you write a single line of code
Act Mode: Build It
Once you’ve got a plan, you switch to Act mode. Now Sixth:- Has all the building capabilities at its disposal
- Can make changes to your codebase
- Still remembers everything from your planning session
- Executes the strategy you worked out together
.png)
Workflow Guide
When I’m working on a new feature or fixing a complex bug, here’s what works for me:- I start in Plan mode and tell Sixth what I want to build
- Sixth helps me explore the codebase, looking at relevant files
- Together we figure out the best approach, considering edge cases and potential issues
- When I’m confident in our plan, I switch to Act mode
- Sixth implements the solution based on our planning
1. Start with Plan Mode
Begin every significant development task in Plan mode: In this mode:%20(1).png)
- Share your requirements
- Let Sixth analyze relevant files
- Engage in dialogue to clarify objectives
- Develop implementation strategy
%20(1)%20(1)%20(1).png)
2. Switch to Act Mode
Once you have a clear plan, switch to Act mode:
- Execute against the agreed plan
- Make changes to your codebase
- Maintain context from planning phase
3. Iterate as Needed
Complex projects often require multiple plan-act cycles:- Return to Plan mode when encountering unexpected complexity
- Use Act mode for implementing solutions
- Maintain development momentum while ensuring quality
Best Practices
Planning Phase
- Be comprehensive with requirements
- Share relevant context upfront
- Point Sixth to relevant files if he hasn’t read them
- Validate approach before implementation
Implementation Phase
- Follow the established plan
- Monitor progress against objectives
- Track changes and their impact
- Document significant decisions
%20(1).png)
Power User Tips
Enhancing Planning
- Use Plan mode to explore edge cases before implementation
- Switch back to Plan when encountering unexpected complexity
- Leverage file reading to validate assumptions early
- Have Sixth write markdown files of the plan for future reference
Common Patterns
When to Use Each Mode
I’ve found Plan mode works best when:- Starting something new where the approach isn’t obvious
- Debugging a tricky issue where I’m not sure what’s wrong
- Making architectural decisions that will affect multiple parts of the codebase
- Trying to understand a complex workflow or feature
- Implementing a solution we’ve already planned out
- Making routine changes where the approach is clear
- Following established patterns in the codebase
- Running tests and making minor adjustments
.png)
Contributing
Share your experiences and improvements:- Join our Discord community
- Participate in discussions
- Submit feature requests
- Report issues
Remember: The time invested in planning pays dividends in implementation quality and maintenance efficiency.