> I’m not convinced tbh, a lot of my colleagues messages are “x broken” or “I do y” … no context whatsoever, and then I have to coax their context for making these decisions.

> Since people started using Claude now I get full context of everything… might be too much sure, but to be honest over-communicating seems better than under-communicating - sure it’s boring and tedious but that shifts the blockage to me.

Yes, but the kind of engineer that used to say "X is broken" will send you some slop with missing context and Claude will try to apply general solutions from its training data rather than from the specific context. As somebody on the Ops side that usually helps devs fixing things here and there, in those cases I'd rather them say "X is broken" and then I ask the question to Claude with all the context I have.

Probably the best solution currently is a shared skill with at least some curated context.