> Should they not produce the findings for someone else to read/validate?

No, they should not. They should not waste others time with output that they themselves do not fully understand. That is not even remotely helpful. The other party can use claude just as easily as they can. Using claude does not add any value in and of itself.

"Hi claude said this thing that I don't really understand please look at it for me" is never useful.

> Should they go back and just open the ticket the old way?

Yes. They should do their damn job while respecting the time of the other people they interact with who have their own different jobs to do.

Replace claude code with your cousin or another employee as a thought exercise.

So write to a colleague asking to finish what your cousin/another employee thinks needs to be done. I think most people would say describe the problem clearly so that I can solve it and be responsible for the fix or let your cousin/other employee finish the job and own the solution.

This is offloading of accountability while denying credit.

Yes, just file a ticket and let the people with relevant expertise and context handle it - obviously. Do software engineers ask Claude for recommendations on handling network outages and bug IT with “AI” slop? Do accountants bring “AI” slop advice to electricians wiring a building? Do lawyers use Claude to try helping physicians diagnose illnesses?

By providing a bad “AI” slop solution that you can’t evaluate, you’re actually creating more work for the people responsible for doing the thing. Now they have to understand the slop you’ve given them, explain why it’s wrong/won’t fit in the existing architecture/has other issue you can’t see without deep context. Or, they have to play politics to ignore your slop without angering you and creating more problems down the line. Either way, it’s harder than just letting them do their job.

Without understanding they have no way of judging the competence of Claude and the slop it generates. So yes they should just file a ticket the old way, after doing the actual hard work, which is reproducing the bug.

I see no harm with sharing an AI analysis in the ticket; it might save the engineer time.