In my scrum team, we basically don't have a vision for the product. Our product owner thinks she's writing user stories but they are really just high level epics. Breaking down those 'stories' ends us up with having to interact with dozens of different stakeholders in the business and gathering requirements for something we have no idea what it is!
My concern with doing this, is that stakeholders don't really know what they need. Each of them might give us conflicting information. Then, each of us on the development team might hold conflicting information and all hell breaks lose when we attempt to build the product.
I'm increasingly feeling that it's the sole responsibility of the product owner to engage all the stake holders, aggregate information they give and form a vision for the product; something it seems, is being farmed out to the development team instead.
Is it a good idea for us developers simply refuse to engage stakeholders? How can a Scrum team encourage the product owner to work with the team in breaking down the user stories?