Whats wrong with the term vibe coding? If it has a negative connotation, the problem isn't the choice of words, the problem is the software being produced. Rather than change the name, try and figure out how to raise the bar.
The term was defined to mean slop. If you are vibe coding you are not doing engineering. I assume most customers don't like hearing that the people working on their code aren't aware in any way of the code they are pushing.
Vibecoding has come to mean "AI slop code" where the people producing it don't understand it, like at all. It can be poorly structured and hard to comprehend.
I believe that train has sailed on this association.
I personally think that there's nothing wrong with vibe coding so long as there are as close to watertight ways, checks and balances to verify that the output is correct. And the best way to do that is to invest domain specific expertise in coming up with as comprehensive a test schema as possible.
If the test schema passes and if your original articulation of intent was correct, then what you have is already very good. From that point onwards, it's the question of accelerating development by just reviewing the output of the LLM and getting it into the right shape.
The combination of the review of the output of the LLM and the review of the test schema and its output, that is going to be a lot quicker to do than coding everything from scratch with a proper design paradigm.