In addition to the nonsensical grammar, "requirements" doesn't mean "shut up." It means we need to understand a lot of information if we (like business analysts or product owners) want to guide a development team to success:

* who our users and other stakeholders are

* their business objectives for the product we're building

* what users need to be able to do with the solution

* their expectations around security, reliability, and many other quality characteristics

* pertinent business rules we must respect or enforce

* interfaces to other systems or pieces of hardware

* how to subdivide and sequence the solution implementation based on priorities

* how to know when we're done with some piece of the work

* how to know if each piece of the work has been implemented correctly

* and on and on

IMHO, equating "requirements" to "shut up" is a ridiculous statement.