After an implementation document is generated, sometimes the plan get's committed without a chance for the user to review it

[dnlopes]

Describe the bug
During a brainstorming > planning session, I already had some instances where Claude generated the implementation plan, and committed it right after writing it to a file, without giving me the chance to review and iterate on it.

To Reproduce
The issue is not consistent. I had occasions where Claude asks for next steps after the plan is created, and other occasions where the plan gets created > committed in one go.

Expected behavior
After Claude writes an implementation plan, it always waits for user confirmation before committing the document.

Logs
If applicable, add logs to help explain your problem.

Additional context
Add any other context about the problem here.

[denolfe]

I ran into this today. I'm fairly certain the way to get around this is to exit plan mode before executing brainstorming. My assumption is that Claude added some stronger language to their prompt when in plan mode.