There's some things called software architecture, requirement engineering and software design. More dev teams should try this.

You don't write a whole app in tests and then write the whole app in code, you make tests for the functionality as you go.

The Test part of TDD isn’t meant to encompass your whole need before developing the application. It’s function-by function based. It also forces you to not have giant functions. Let’s say you’re making a compiler. First you need to parse text. Idk what language structure we are doing yet but first we need to tokenize our steam. You write a test that inputs hello world into your tokenizer then expects two tokens back. You start implementing your tokenizer. Repeat for parser. Then you realize you need to tokenize numbers too. So you go back and make a token test for numbers.

So you don’t need to make all the tests ahead of time. You just expand at the smallest test possible.

I don't know if you're joking or not. I suppose tdd will help know what you need before you start.