What should be the ideal 100% TOR for a developer?

Question

Preparation of terms of reference

Hello, dear "toasters". I myself am from the world of marketing, sometimes I take part in the development of TOR for technical specialists for the implementation of improvements in the Frontend, Backend areas.
Bottom line: sometimes I notice a little grumbling from technical specialists, they say, not quite perfect, accurate technical specifications.
Q: How can I make TK more ideal? Can you show examples of ideal TK?
By TK - I mean: 1) UX prototypes and 2) The TK itself in the document - step-by-step, precise points (there is a problem somewhere).
I shoveled the Internet in search of examples, I borrowed something, the best, But it's still not right.
PS: I just want to improve communication with developers, make their work easier :).

Answer 1

Ideal TOR - when the developer does not have additional questions, and the result of the developer's work suits the customer the first time.
This does not happen, but the closer to the above - the better.
It is difficult to borrow anything from other people's TK - there are always some nuances.

Answer 2

At least you understand that technical specifications are necessary ... This is already a level above average

Answer 3

Shitty developers just grumble, you can ignore such people. Normal developers understand what teamwork is and give constructive comments.

Answer 4

Detailed TOR without contradictions, written in a competent and understandable language.
Breakdown is required. It would be nice to illustrate the location of objects with screenshots.

Answer 5

Well, I think that such a TK, in principle, cannot exist, because while you write such a TK, you will have time to grow old :)))
In general, start with use cases. Scenarios are not a panacea but lead the development team to understand why and what is needed. It also helps the customer understand what he wants from the system.
If you imagine only a set of functions without scripts, nothing sensible will work.
Well, according to a good TOR, this is a living document, and it should improve as it is developed. Even according to GOSTs, changes can (and in my opinion - should) be made to it, but everyone must agree on these changes, i.e. both customers and developers...