Calling phase execution automatically after planning would be nice

[gyuszka92]

Is there a situation where after the planning of a phase is finished, we don't want to call the execution right away?
Would be nice to have a plan-and-execute phase command which would remove the manual "work" of calling the "execute phase" command when the planning is finished.

[lydonator]

The problem with that is having access to clear the context. There is no claude code hook that can be called to clear the context in a running query/agent. Without this, even with sub agents you would quickly run out of context in the orchestration thread.

[AshExplained]

Call me mad but Sometimes I like to plan all the phases first and get the plan documents ready before execution

[gyuszka92]

@lydonator hmm...let's see if I can find a workaround.

@AshExplained exactly 😎

This is one of the main challanges this project brings. Finding the perfect balance between milestone sizes, pre-planning and maximizing the time claudr code can run by itself with no interraction by us.

For example, if an integration planned for phase 2 introduces new variables into the .env files (which I need to do manually) and another integration in phase 5 requires some setup in Google Cloud console, I would like to do those steps at the planning of the whole milestone, not after each phase is executed, so claude code can run in an extended time interval independently.

[Tibsfox]

Submitted a fix for this in PR #823 — the `<offer_next>` section in plan-phase.md now uses AskUserQuestion to offer:

1. Execute Phase {X} (recommended) — run all plans now
2. Review plans first — inspect before executing
3. Clear context first — /clear then /gsd:execute-phase for a fresh window

This only fires in the non-auto-advance case. When auto-advance is enabled (step 14), the transition already happens automatically. So this fix is specifically for the interactive workflow — offering the user a choice rather than forcing execution, which is exactly what the issue requested.

Complementary to autopilot mode (#796) — autopilot chains automatically, this fix improves the interactive experience.