My org, like every org, is struggling with this as well. We find ourselves writing skills like `/decomment` and often running several "minimize" passes on PR descriptions, etc.
One thing that has markedly helped is tweaking our AGENTS.md prompt and prose-heavy skills like `/pr` or `/ticket` to specify that all technical output needs to be written in ASD-STE100 Simplified Technical English. It has helped us so much. We still have to `/decomment` or minimize to remove unnecessary stuff that's been written in ASD-STE100, but the output is a lot easier to digest.
OTOH, we have a guy in marketing that has taken it upon himself to use Claude to draft these wildly complicated and dense implementation specs that he doesn't understand for various things that he just hands off to my team to implement. He has no context for how our product is built, the various layers and their interactions, etc. so they're often flat out wrong and overly complex, invent systems that do not exist, all of that. Then he gets mad that we're not moving as fast as he wants, because he gave us the implementation spec! I have been struggling to come up with a way to diplomatically tell him that his actions are slowing us down, and if he'd just describe what he needs instead of speccing it himself, we'd be twice as fast...
One thing that has markedly helped is tweaking our AGENTS.md prompt and prose-heavy skills like `/pr` or `/ticket` to specify that all technical output needs to be written in ASD-STE100 Simplified Technical English. It has helped us so much. We still have to `/decomment` or minimize to remove unnecessary stuff that's been written in ASD-STE100, but the output is a lot easier to digest.
OTOH, we have a guy in marketing that has taken it upon himself to use Claude to draft these wildly complicated and dense implementation specs that he doesn't understand for various things that he just hands off to my team to implement. He has no context for how our product is built, the various layers and their interactions, etc. so they're often flat out wrong and overly complex, invent systems that do not exist, all of that. Then he gets mad that we're not moving as fast as he wants, because he gave us the implementation spec! I have been struggling to come up with a way to diplomatically tell him that his actions are slowing us down, and if he'd just describe what he needs instead of speccing it himself, we'd be twice as fast...