I do all my development as a longish running pipeline that mimics how I used to write software.

There is a high-level plan, it gets decomposed into steps that get performed sequentially. If during a step something occurs that challenges the original assumptions, the remaining steps can be reconfigured or the implementation stopped.

Well, I guess it's more rigorous than me, because it does a lot of quality checking along the way and if course, in the end.

This is the most boring approach to this work as you can imagine. But, after running this process hundreds of times and tuning it, today I can do about 10-20 PRs a day that are often quite good. I manually review and manually test and as models and my pipeline have improved the % of PRs that require zero human intervention after the initial planning is getting higher. Maybe 50%. For the other half, it's good, but there are often glaring bugs, especially for UI/UX stuff.