

test dogmatist detected
No, the bottleneck is not always requirements. Understanding requirements is a prerequisite to writing correct code, but it takes a fraction of the time.
Obviously different domains have different complexities of requirements and code which changes the ratio




Instead of spending 4 weeks writing requirements and 1 week implementing them, have you tried spending a day guessing at requirements, half a week writing a prototype, and then asking the customer if it works for them?
Have you ever worked on a tools team where your customers are internal and your developers are also customers and so know the requirements inside-out?