-
Notifications
You must be signed in to change notification settings - Fork 743
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow retaining specific context across multiple plans #155
Comments
I like this idea and definitely want to add features along these lines. I’m thinking of two features: one that allows Another is reusable context blocks that can be loaded into multiple plans. So pretty similar to what you’re envisioning. I think the idea of loading context by default for new plans is also interesting and I’ll think about this too. Thank you! 🙏 |
Both suggestions seem reasonable to me. If you would "... allow[s] plandex load to accept a plan name ..." do it the following way, you could reuse more of the already existing functionality, which would be a nice bonus. For me, it is important that I can work efficiently. The following I would consider a not-so-good solution:
Instead, allow the following:
Or even better, allow creating a plan named "default" which from which the context will always be pulled when Thank you for considering it! |
Description
Plandex currently lacks functionality to retain specific files across multiple plans, particularly when creating new plans using the
plandex new
command. This is essential for consistently including files like software architectural information, dependency definitions or the database schema during plan execution.Requirement
Introduce a feature to load context that ensures specified files are automatically included in any new plan created.
The text was updated successfully, but these errors were encountered: