For agile software projects, it should be kept in mind that one of the agile values is "Working software over comprehensive documentation", which does not mean 'no' documentation. Agile projects tend to stress the short term view of project needs; documentation often becomes more important in a project's long-term context. What's the big deal about 'requirements'?
For agile projects, which may be more
amenable to changing requirements, detailed documented requirements may not be needed. However some type of documented specfications are still important, in the form of user stories or something similar. In agile projects, some or all requirements may be embodied in user stories.