> Maybe it's because I spend a lot of time breaking up tasks beforehand to be highly specific and narrow, but I really don't run into issues like this at all.

I'm looking at the ticket opened, and you can't really be claiming that someone who did such a methodical deep dive into the issue, and presented a ton of supporting context to understand the problem, and further patiently collected evidence for this... does not know how to prompt well.

Its not about prompting; its about planning and plan reviewing before implementing; I sometimes spend days iterating on specification alone, then creating an implementation roadmap and then finally iterating on the implementation plan before writing a single line of code. Just like any formal development pipeline.

I started doing this a while ago (months) precisely because of issues as described.

On the other hand,analyzing prompts and deviations isnt that complex.. just ask Claude :)

The methodical guy confused visible reasoning traces in the UI with reasoning tokens & used claude to hallucinate a report

Sure I can.