You can fill the gaps with more "Vibe Coding."
While one agent is busy, you can start another agent on a different task. (Or maybe even the same task with a variation in the prompt. To hedge against the unlikeliness of the first agent always one-shotting acceptable code.)
Even if you aren't verifying the resulting code, prompting six different agents and confirming their results should keep you busy. (I guess you could even do more if you wanted...)
I have seen various descriptions of this type of workflow. Most recently: https://hw.leftium.com/#/item/45180353
> Now I see him spending most of his time doing what product managers traditionally do: talking to users, understanding their problems deeply, figuring out what's actually worth building. Coding has become maybe 20% of his job, and even that 20% is mostly about understanding requirements and translating them into clear specifications. The actual implementation work that used to consume 80% of his time is now handled by machines.
Also here is a short video of this type of workflow in action: https://www.youtube.com/shorts/tP1fuFpJt7g