Plan & Act

Plan & Act modes embody Sypha's methodology for structured AI development, prioritizing thoughtful planning prior to implementation. This dual-mode framework assists developers in creating more maintainable, accurate code while minimizing iteration time.

Plan Mode: Think First

Plan mode serves as the space where you and Sypha determine what you're attempting to construct and your construction methodology. Within this mode, Sypha:

• Possesses the ability to read your complete codebase to comprehend the context
• Will not implement any modifications to your files
• Concentrates on comprehending requirements and developing a strategy
• Assists in identifying potential issues prior to writing a single line of code

Act Mode: Build It

After establishing a plan, you transition to Act mode. Now Sypha:

• Possesses all the building capabilities at its disposal
• Can implement changes to your codebase
• Retains everything from your planning session
• Executes the strategy you developed together

Workflow Guide

When I'm developing a new feature or resolving a complex bug, here's my effective approach:

1. I begin in Plan mode and communicate to Sypha what I want to construct
2. Sypha assists me in exploring the codebase, examining relevant files
3. Together we determine the optimal approach, considering edge cases and potential issues
4. When I'm confident in our plan, I transition to Act mode
5. Sypha implements the solution according to our planning

1. Start with Plan Mode

Initiate every significant development task in Plan mode:

Within this mode:

• Communicate your requirements
• Allow Sypha to analyze relevant files
• Participate in dialogue to clarify objectives
• Develop implementation strategy

2. Switch to Act Mode

After establishing a clear plan, transition to Act mode:

Act mode enables Sypha to:

• Execute according to the agreed plan
• Implement changes to your codebase
• Preserve context from planning phase

3. Iterate as Needed

Complex projects frequently require multiple plan-act cycles:

• Return to Plan mode when encountering unexpected complexity
• Utilize Act mode for implementing solutions
• Maintain development momentum while guaranteeing quality

Best Practices

Planning Phase

1. Be comprehensive with requirements
2. Communicate relevant context upfront
3. Direct Sypha to relevant files if he hasn't examined them
4. Validate approach prior to implementation

Implementation Phase

1. Follow the established plan
2. Monitor progress according to objectives
3. Track modifications and their impact
4. Document significant decisions

Power User Tips

Enhancing Planning

• Utilize Plan mode to explore edge cases prior to implementation
• Transition back to Plan when encountering unexpected complexity
• Leverage file reading to validate assumptions early
• Have Sypha create markdown files of the plan for future reference

Common Patterns

When to Use Each Mode

I've discovered Plan mode performs optimally when:

• Initiating something new where the approach isn't evident
• Debugging a complex issue where I'm uncertain what's wrong
• Making architectural decisions that will impact multiple parts of the codebase
• Attempting to comprehend a complex workflow or feature

And Act mode is ideal for:

• Implementing a solution we've already planned out
• Making routine modifications where the approach is clear
• Following established patterns in the codebase
• Running tests and making minor adjustments

Contributing

Share your experiences and improvements:

• Join our Discord community
• Participate in discussions
• Submit feature requests
• Report issues

---

Remember: The time invested in planning yields dividends in implementation quality and maintenance efficiency.