I can’t find it now but there was a pretty good blog post on HN(it was marketing a product to solve this problem, but felt legit). That basically divided game development into four stages. Stage 1 is you can just one shot vibe code the boiler plate, stage 2 is you can like more specifically vibe code certain features, then I forget specifically, but like you have to have pretty deep subject matter expertise to handle the networking code.

(This was written by someone with game development experience I believe)

No, "vibe coding" means you don't look at the code, nor care about it. You could probably manage to get together a prototype, maybe even get it to deploy, but eventually it'll fall over in it's own slop. The tooling isn't ready for a non-software engineer to maintain a large-scale software project, don't let the marketing fool you.

However, if you are a software engineer, armed together with an agent, I don't see why not. Come up with the architecture/design, stick to it, and you could probably get something to a polished state at one point.

Assets are the main bottleneck.