Yes. "When can I start" tries to cover this but it is realy hard to make it air tight. Maybe you can try to start with the real project if the prototype you have been developing has all the features you want in the game. Is that a better phrasing of the step?

Really new programmers are very much focused on their dream game. Trying to talk them away from it may be counter-productive (only in step 5 I can do what I really want??? Oh man, this guy is so wrong!). Rather than selling the first games as "quick and throw away", they'd better be steps towards the real game (even if they are in reality discarded).

Maybe add one small thing each iteration until finished?

If you can't make it work, make it smaller

If you can't make it work, write a small experimental game with the new thing?

The big danger is that "small thing" is way too big in reality, new programmers over-estimate the step-size they can take.

It needs a careful explanation how small a small thing really is, and that it's useful to do experiments elsewhere, and copy the results.

New programmers don't understand the solution structure is important rather than solution itself.

I need some pretty beginner-friendly tutorial because I also need the knowledge on how to design a Zelda-esque game. That and I'm just not confident enough to code on my own.