Claude, write a skill to create design docs as per this blog post /s

In all seriousness a big chunk of my work is reviewing docs and 100% of the design docs I read these days are generated and there is a lot of slop. I have to parse them with AI to make sense of them, contributing to the problem. I wish people would follow a sensible set of rules like this one.

Did anyone have any solution to this dread? Or cracked the code on how to write docs that have other agents as their primary audience?

▲

1over137 2 hours ago | parent [-]

>Did anyone have any solution to this

Yes. Don’t “write” your design docs with AI. If you can’t personally enforce that, get your manager to.

	▲	mckn1ght an hour ago \| parent \| next [-]
		I’d say don’t bother trying to parse it alone. Have a meeting where the person that created it presents it, and drill into anything weird. If you can back them into a corner and force them to admit they don’t even understand something they supposedly wrote, use that as an opportunity to remind people it’s not acceptable to generate design documents that you don’t understand and then push them off onto other people.
	▲	AnimalMuppet an hour ago \| parent \| prev [-]
		Yeah, this. If it's slop, reject it, and tell them why.