1. I understand some types of development cycle. I work as a software consultant/developer for a number of different companies/gov. agencies, generally going in at all points of the cycle to write specs, develop code, fix bugs or review implementations and architectures and make best practice recommendations or identify security flaws.
2. Meaningful to who? Personally I prefer working with {well written/structured/patterned} but undocumented code (with decent unit tests), over {badly written/badly structured/no cohesive design patterns} code with volumes of documentation but no test cases.
3. No.
4. No, never heard that expression, and it also makes no logical sense to me. (I have heard something similar about having to crawl before you can walk, and having to walk before you can run, but not the particular variation in OP)
5. No.

So I can answer with a straight yes to none of them.