Yes, hence tests, linters, and actually verifying the changes it is making. You can't trust anything the LLM writes. It will hallucinate or misunderstand something at some point if your task gets long. But that's not the point, I'm not asking it to solve things for me.

I'm using it to get faster at building my own understanding of the problem, what needs to get done, and then just executing the rote steps I've already figured out.

Sometimes I get lucky and the feature is well defined enough just from the context gathering step that the implementation is literally just be hitting the enter key as I read the edits it wants to make.

Sometimes I have to interrupt it and guide it a bit more as it works.

Sometimes I realize I misunderstood something as it's thinking about what it needs to do.

One-shotting or asking the LLM to think for you is the worst way to use them.