Thought Driven Engineering: The Happy Path (EPISODE 1)

I usually don't, but I understand that some people sometimes have code feet. I'd say anytime that happens take a step back, review your solution and documentation again, think about any edge case you may have missed, think about other solutions to the same problem. The idea is to look at your train of thoughts long enough to get your motivation to actually "write code" as you only solved the problem in theory and not yet in practical.
My advise will be to take time, review your solution, think about the impact of your solution (cost/time wise) to you and to the users/consumers, and find motivation to do the work.