If the problem is identifying requirements in the first place, one practice I would recommend is dogfooding. Sometimes teams will narrow their focus on just the exact features they're developing and the precise success criteria that a customer or dev manager has defined ahead of time. Possibly they may even state a feature has been completed when it only passes unit tests but they haven't actually tested the feature directly by interacting with the application as a whole. When people include directly using the product as part of their development activity, gaps and corner cases become obvious much sooner. Everyone, including developers, should be using the application as a whole and playing around with it. Try resizing the screen, or using unusual gestures, or entering odd data into it - whatever is applicable - to see if something jumps out as missing or broken.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
If the problem is identifying requirements in the first place, one practice I would recommend is dogfooding. Sometimes teams will narrow their focus on just the exact features they're developing and the precise success criteria that a customer or dev manager has defined ahead of time. Possibly they may even state a feature has been completed when it only passes unit tests but they haven't actually tested the feature directly by interacting with the application as a whole. When people include directly using the product as part of their development activity, gaps and corner cases become obvious much sooner. Everyone, including developers, should be using the application as a whole and playing around with it. Try resizing the screen, or using unusual gestures, or entering odd data into it - whatever is applicable - to see if something jumps out as missing or broken.