My suggestion is to use best practices for user story creation, like to follow the INVEST principle, also you need to have Grooming sessions for your stories which would go into sprint. You should practice static testing of your available design documents and available requirement - while doing that you could find missed requirements. Try to create FAS (feature analysis specifications). Also you can try to assign a role of requirements analyst to one tester or dev.
In short, it all depends of what sdlc/stlc you are following.
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.
My suggestion is to use best practices for user story creation, like to follow the INVEST principle, also you need to have Grooming sessions for your stories which would go into sprint. You should practice static testing of your available design documents and available requirement - while doing that you could find missed requirements. Try to create FAS (feature analysis specifications). Also you can try to assign a role of requirements analyst to one tester or dev.
In short, it all depends of what sdlc/stlc you are following.