Should I cover every single user flow including error states in wireframes for web and mobile applications?

While creating wireframes, I mostly create the obvious screens and flows, and leave out all the micro flows like error states or less important screens. These are then fleshed out when creating the high-fidelity prototype. But due to this, I often end up missing screens that the developer then has to work with me on to build out. In some situations we miss out on the screen entirely resulting in users winding up in dead ends.

One way I thought to solve the problem was to create detailed task flows and then using the task flows as a reference to create wireframes that cover every single flow. But my concern is that this is going to end up being an unnecessarily time consuming effort.

Have you followed this process and seen good results? Is it worth the extra time? Can I just create detailed task flows and skip creating detailed wireframes and go directly to the low-fidelity mockup? (will still wireframe high-priority flows)

Any advice is appreciated. Thanks in advance.