I think anything vague is and should be pushed back. If we do not know the complete user story, then it is not a feature. The problem needs to be well defined b

I think anything vague is and should be pushed back. If we do not know the complete user story, then it is not a feature. The problem needs to be well defined before discussing with the engineering team. Example: We are building a desktop app. Now the management want to have a "login" page in the desktop app. This is a very vague statement to be discussed with engineering. First decide on who can login, how can one register, is the login possible only when the device is connected to the interenet., are we going to limit features of the app based on subscription, etc.