If you work at "product manager" level, that would be vibe coding, as you prompt for functional and non-functional changes and you review the behavior and characteristics of the program, not the code generated.

I believe the author was trying to specifically distinguish their workflow from that, in that they are prompting for changes to the code in terms of the code itself, and reviewing the code that is generated (maybe along with also mentioning the functionality and testing it).