Plan & Agent

Plan & Agent modes represent PostQode's approach to structured AI development, emphasizing thoughtful planning before implementation. This dual-mode system helps developers create more maintainable, accurate code while reducing iteration time.

Plan Mode: Think First

Plan mode is where you and PostQode figure out what you're trying to build and how you'll build it. In this mode, PostQode:

• 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

Agent Mode: Build It

Once you've got a plan, you switch to Agent mode. Now PostQode:

• 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

Workflow Guide

When I'm working on a new feature or fixing a complex bug, here's what works for me:

1. I start in Plan mode and tell PostQode what I want to build
2. PostQode helps me explore the codebase, looking at relevant files
3. Together we figure out the best approach, considering edge cases and potential issues
4. When I'm confident in our plan, I switch to Agent mode
5. PostQode implements the solution based on our planning

1. Start with Plan Mode

Begin every significant development task in Plan mode:

In this mode:

• Share your requirements
• Let PostQode analyze relevant files
• Engage in dialogue to clarify objectives
• Develop implementation strategy

2. Switch to Agent Mode

Once you have a clear plan, switch to Agent mode:

Agent mode allows PostQode to:

• 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-agent cycles:

• Return to Plan mode when encountering unexpected complexity
• Use Agent mode for implementing solutions
• Maintain development momentum while ensuring quality

Best Practices

Planning Phase

1. Be comprehensive with requirements
2. Share relevant context upfront
3. Point PostQode to relevant files if he hasn't read them
4. Validate approach before implementation

Implementation Phase

1. Follow the established plan
2. Monitor progress against objectives
3. Track changes and their impact
4. Document significant decisions

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 PostQode 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

And Agent mode is perfect for:

• 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

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.