While I kinda agree on this method, there is one particular point worth emphasizing on: once your tasks are laid out, you need to ask two questions.
What kind of pain in the ass is missing from the list?
Which one of those tasks have never been done by the team?
Just sit there and challenge everything again and again. Don't let anything in oversight. And certainly do not focus on the main features since there is an increasing number of pain in the ass coming to get you (GDPR to pick a recent one, but also password reset, email validation, user preferences, email unsubscription, ...).
Regarding the things you have never done, you need to do preliminary PoCs to estimate how long it's going to take. If you can't sell this, then put those tasks ahead in your planning (the riskier the task the first it should be done) and be ready to re-adjust scope or deadline.
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.
While I kinda agree on this method, there is one particular point worth emphasizing on: once your tasks are laid out, you need to ask two questions.
Just sit there and challenge everything again and again. Don't let anything in oversight. And certainly do not focus on the main features since there is an increasing number of pain in the ass coming to get you (GDPR to pick a recent one, but also password reset, email validation, user preferences, email unsubscription, ...).
Regarding the things you have never done, you need to do preliminary PoCs to estimate how long it's going to take. If you can't sell this, then put those tasks ahead in your planning (the riskier the task the first it should be done) and be ready to re-adjust scope or deadline.