That might emerge as one of the main tasks of future software engineers, writing formal specifications by hand.
It could be the case that Tony Hoare was right, just too early.
Yes! Formal specs could be where the understanding of what exactly the system is supposed to do gets laid out - and ideally coupled into the verification process that the code produced actually does what it is supposed to (and nothing else...). That would be a big change!
It is normal to spend a huge amount of time creating incredibly detailed behavior specs in avionics and other code where people can die from bugs.