I wonder if anyone was in a similar situation and can advice as to how manage requirements best. I am responsible for user stories writing. However, I receive requirement in form of traditional specs often very ill formed and ambiguous. I am also getting wireframes together with spec. what I end up doing is converting requirements from the spec into user stories filling out all gaps along the way. by doing so I effectively do backlog definition and grooming at same time which seems to be incorrect. This is because developers don't look into product spec so I have to outline everything in user stories.
any suggestions on how to improve the whole process? one constant in this process at the moment is that I receive all requirements from product and have very little control on what I can redefine.