I just finished implementing one feature. Take aways:

* It is not *much* faster than just vibe coding.

* This outputs a more robust solution, but you still need to be in the middle.

* Reviewing the plan (as they suggest in the video) is not really suitable. The plan is long kind of slop. You really need to find the right things that are important.

* Reviewing code is still a must for me.

* We need to specify a process to handle feedback: PR comments, bugs and Plan changes using the same approach.