Broadly, I kinda feel like you're comparing Agile and Waterfall. If I'm "Valuing people over processes" I'll quite likely stop at #1, and rely on my people/tea

Broadly, I kinda feel like you're comparing Agile and Waterfall. If I'm "Valuing people over processes" I'll quite likely stop at #1, and rely on my people/team to work out the plan (#2) and supplies (#3) and task breakdown (#4) amongst themselves. This does though, require a team willing and capable of resolving ambiguity, who'll proactively communicate their decisions and ask for assistance/resources. Your "uncommon problem" of lazy professionals is always going to be a killer, but if you're trying to do (original manifesto style) Agile with a team who're not confident or experienced enough to make it work - you'll end up with a way worse outcome from ambiguity than with an experienced/confident "Agile team".