Skip to content
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

Open
appreciated opened this issue Jun 24, 2024 · 2 comments
Open

Allow retaining specific context across multiple plans #155

appreciated opened this issue Jun 24, 2024 · 2 comments

Comments

@appreciated
Copy link
Contributor

appreciated commented Jun 24, 2024

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.

@danenania
Copy link
Contributor

I like this idea and definitely want to add features along these lines.

I’m thinking of two features: one that allows plandex load to accept a plan name or index as a parameter—all the context from the passed in plan would then be loaded by the current plan.

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! 🙏

@appreciated
Copy link
Contributor Author

I’m thinking of two features: one that allows plandex load to accept a plan name or index as a parameter—all the context from the passed in plan would then be loaded by the current plan.

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:

pdx new
pdx l --plan "some-plan"

Instead, allow the following:

pdx new --with-context some-plan-name 

Or even better, allow creating a plan named "default" which from which the context will always be pulled when pdx new is being executed

Thank you for considering it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants