Planning is always useful as it aims to discover and define what you need to do before you begin.
What you're referencing is more to do with process, how you produce code. And on this level I'd agree you don't need to document things like methods before you write them. Instead write a test based on the requirements, rules and examples, write a method to fulfill the test, document the method.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.