Reusable Specifications, code is disposable!!

Resusability and Loose Coupling are the panacia of Enterprise development, the drive to reduce cost and complexity through reusability and loose coupling, but the actual result has been poorly built components (the eternal MVP) and tight coupling, resulting in the big ball of mud.
What if the reusability objective was at the specification layer, with the code being a disposable implementation? easily generated, over and over?