I'll be honest - half the time it's trying to keep it from other engineers who are overly eager to have an opinion because a) they're low-output and looking to posture, and/or b) or want things to be done a different way.

At least the business side of the house appreciates the spec'd work being accomplished.

Intentionally not communicating things in order to prevent bikeshedding is a dangerous game to play and a symptom of a broken environment, but that doesn't mean it's not sometimes a valid approach.

Agree - and it 100% comes from broken teams/environments/people. In engineering, I find most teams are more invested in tearing each other down more-so than building each other up - that's admittedly very anecdotal and personal to me.