Everyone agrees that catching errors in the design phase is far superior to catching them in implementation or testing phases. So why are requirements often me

Everyone agrees that catching errors in the design phase is far superior to catching them in implementation or testing phases. So why are requirements often mentioned only in passing ? Don't they deserve some intellectual TLC ? Writing good requirements is at least as challenging as writing good laws. And then, as the article suggests, an AI can kind of fill in the missing bits if it has good cultural context. There's many good tools now for formulating and managing requirements. Why do I not see papers about how LLMs benefit from them ?