You're confused about the difference between detailed design and coding.
From a comment you posted:
during the detailed design. The way I see it, the Design phase would comprise 2 stages : High-level and Detailed. While "High-level" would identify the data structures and list of programs, Detailed design would spell out the logic. If the logic is stated only in words, it leaves risk at the coding level - can the logic be accurately translated into code in a timely manner? Therefore, it would be a risk-mitigation device to design the code as well.
As of 2018, skilled humans are still required to create useful software. Don't let all the machine learning hype fool you, human skill, not process, is still the most important link in the chain.
If the logic is stated only in words, it leaves risk at the coding level - can the logic be accurately translated into code in a timely manner?
Turning logic described with natural language into logical instructions a machine can perform, is the fundamental skill of software developers. That process has to be done somewhere. That risk is going to be present, as long as us humans are in the process. You think you are mitigating the risk, but you are just moving it and making it more expensive.
What you are describing here, is turning "coders" into typists. Doing so is not going to bring you any benefit, but it will bring you substantial cost. You've already realized some of the trouble you are inviting to yourself. You could write an entire software program in MS Word, then hand it off to someone else to brainlessly copy into an IDE. But like you are concerned about, MS word doesn't do any compilation checks. None of the tooling is there. And what's the likelyhood you can write a multi-thousand line program, and have it work flawlessly on the very first test? Pretty unlikely. Now your typist has to go back to you and you have to edit your MS word document, and try again over and over, with a huge hassle and cost each time. You've realized the risk of coders taking too long to write the code, turning it into the reality of someone else writing the code, using a really god-awful development environment, and took just as much or longer to accomplish nothing.
At some point you realize, since the person writing the Word doc is the only one you trust with the fundamental skill to do the actual programming, maybe that person should just be the one to type everything into the IDE in the first place.
Natural spoken languages are very poor language for communication of super-precise subject matters. Spoken languages are incredibly context sensitive. Programming languages do not. A detailed design is written ideally in the sweet spot between natural language and technical language, with the point on that spectrum varying based on skill of the developers and the risk of the project.