You still need someone at the wheel with a strong sense of where the architecture should go. If you just let AI drive, it goes in circles forever.
Just had this experience at work. I tasked a mid-level engineer to architect a brand new complex system with AI assistance and he spent a month burning tokens trying to get everything specified. Between AI going down irrelevant rabbit holes and him not being assertive enough over the AI, it didn't work. After a month, there were still tons of open questions, undecided workflows, etc. I wanted to try this as an experiment, and to give him the opportunity, but it didn't work. And this person is not at all incompetent, just doesn't have enough experience in big-picture system design.
I reassigned a very senior engineer to take over the project on Monday and in a few days (writing this on a Thursday night) the design is done and implementation is well under way.
Ai is not a magic silver bullet. It's a wild horse and you need a master horseman to tame it.
This does not match my experience. At work I have AI write architecture docs for complex features based on requirements that the product team collects. When staff engineers review those docs, in the overwhelming majority of cases the only issues they can find can be characterized as nits or bike-shedding. In contrast, AI can find problems and even serious gaps in architectures designed by the most seasoned engineers on the team (because those engineers have been doing their best to resist using AI).
So I think the whole "AI can write good code but it cannot design architecture" is just cope. It's where the goal posts have been moved to after it became impossible to deny that AI can actually write good code. Next up it will be "AI can write good code and design good architecture, but it has no taste". Indeed we're seeing various of that already.