Design cannot happen in a vacuum. Good design is iterative and collaborative. It's reasonable to expect tasks to be well defined and well scoped. It's also tr

Design cannot happen in a vacuum. Good design is iterative and collaborative. It's reasonable to expect tasks to be well defined and well scoped. It's also true that the other roles that you are deriving your tasks from, are not ONLY scoping out tasks for you 100% of their time. So collaborate, a ticket might have been written in haste, without all the information from a customer or stakeholder, and with the intention that it still needs to be fleshed out. You should communicate what you need and work together. You seem to want fully implementable tasks to be thrown over the wall to you to implement. Businesses will never build anything great working like that. questions/answers: 1) (poor specs) yes but maybe not for bad reasons 2) (improve quality)communicate what works for you and find out what works for them, write a template.md file for what a good specification looks like and have them use that as a template. 3) (should engineers have a say?) Yes! This process should be a collaboration between the whole product team including you! 4) input is more appropriate than 'control' 5) Respectfully, I think you're underestimating the tasks of those other roles that you don't see. For any non-trivial product in a non-micro company with a tiny customer base this is not possible.