Question: How are we supposed to update a plan before the implementation phase?

I had conductor start a new track with a plan document, but upon review I wanted to give more feedback. Assuming it's a non-trivial feature, I can imagine there could be a round of brainstorming/ interactive back and forth before we have a good plan in place. However, when I gave it the feedback and asked the Gemini CLI to update the plan, it went ahead and started implementing. So I don't have a chance to even try the conductor:implement feature.

I'm just curious on how you guys see the workflow work for this case, and in general how should one manage work between conductor and non-conductor prompts?

Thanks!

The issue names no files, tests, or entry points to inspect. It asks for guidance on updating a plan before implementation and coordinating Conductor with other prompts; done would be a documented workflow answer clarifying that process.