When writing a full Technical Spec - defining in details what every part of the system will do, show and look like - does it help to state the obvious?
Let's take the easiest example:
A Login Screen needs fields for username & password and their limitations. Those details need to be described.
But (assuming you've never done this before and can't copy from another spec) does it suffice to say: Include "lost password link" and assume the engineers are mature enough to know what to do.
Or should it go into the details of what happens when you click on that link, what the text of each stage says and what the arbitrary timeout limits are?
Or should it say "...and behave like ____________ does, and a pointer to some other product?
Would there be any advantage to writing 2 - 3 pages with all the details, or will this type of detail be counter-productive, similar to micro-management?