First time I've heard of anti-requirements, though it seems I've kinda used them albeit more directly. For example I'll just ask "I assume the description does not depend on the price, is that assumption correct?"

Another thing I've noticed is that stakeholders mostly think about the everyday stuff and thus can forget about edge cases. I've been in several projects where "never ever" turned out to mean a few times a year. Feels like asking about such anti-requirements like in the article could be very prone to this.

On another note, the example used in the article feels contrived. Like why such a denormalized shopping cart entity to begin with?

It also misses an obvious requirement, that the customer should get the quantity paid for. Or at least describe how to handle properly updating cloned attributes like Quantity. Ie what if one of the systems fails to update an increase in Quantity?