But in doing so I kinda recognize the irony that I would absolutely do the same myself. I hate planning, I tend to start as quickly as possible with programming. And because of that, I tend to get stuck in similar ways.
Same. I struggle to know where to start, and find if I just start, I eventually figure it out. A colleague of mine has nailed this. He begins with the documentation. Outlining all the functional requirements, then reviewing and iterating. It helps to have multiple sets of eyes review, including the stakeholders/customers. Once that's locked in, the development is super smooth. It's clear where to start, what the architecture looks like, and who needs to be involved. In fact, once the documentation is locked in, it's very easy to get an LLM to build it competently. Plus no surprises because the stakeholder/customer has approved all the requirements.