Writing a spec thorough enough for AI to generate code that verifiably meets in and solves your problem means you're still programming, but specs instead of systems.
Regardless, the studies have already demonstrated this: As you go higher-level, you write roughly the same amount of code and bugs per line, but also implement more features per line.
An AI tool will be ready for use when it demonstrates that same capability of "same bugs per line, more features per line".
Just the step from "program" => "spec" is already a big one. So big, that it is rarely done today. Test-driven development is an attempt at this, but the problem is that tests cannot truly verify a spec. Proofs can. Of course, you can combine tests and proofs, for example proofs for correctness, tests to make sure other measures like speed and cost are sane. But if you want to be absolutely sure, you will need to replace all tests by proofs.
Most people don't understand proof, but if you don't understand proof in 10 years, you will be out of a job as a programmer.
No, that's not gonna happen. Can you write a proof of an order for you go to go a fresh market to buy ingredient of a menu I want to cook? "Hey, go buy ingredients for my noodle menu whose result is my taste"