I think this is a really good insight. It's definitely the back and forth in Claude Code or whatever harness you use that breaks flow and leads to frustration. This seems to be what Fable is solving since it is capable of doing much larger chunks of work without needing input constantly. Having a much more involved planning session than just turning on plan mode and then handing that off to be implemented is a much better approach. It's sort of what I've arrived at by accident where I often start planning changes in the web app and spend a long time going into detail about my vision and then working through the details without having Claude write any code other than perhaps a few small exploratory artifacts to visualize certain things and then taking all of that and moving over to Claude Code for implementation.