You mentioned "coming back later" but being in the zone. That's the part I want to understand. So this metaphor isn't helping cause the conductor is constantly working, constantly seeing the output. Not coming back later.
My zone is the big-picture zone. What are we building, what needs to be done, how do the interrelated bits all come together? I can tell an agent "go implement X" and start planning Y that comes after it.
I don't really get in the zone for raw code typing, that's always been a slog.
I point at the violins. I gesture the drums upwards. Sometimes I make a big broad gesture that encompasses the entire orchestra.
My agents are tasked, in part, with explaining the context with mockups and examples I can poke at for each job.
I don't really get in the zone for raw code typing, that's always been a slog.