You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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
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: