Using Prototypes for more than just user-testing

Other than for user-testing purposes, PM, Dev and QA are asking the designers in our company to create prototypes to be used as a guide along side of annotated wireframes and visual specs and the actual stories.

In a perfect agile world this may work, but being a shared resource designers, it doesn't seem feasible.

Other disadvantages I see include, needing to fully built out every single interaction in the prototype. Also, Dev and QA can easily miss interactions since there are no specs in the wireframe calling out specific logic or interactions.

Are there any designers out there efficiently providing prototypes as deliverables? Are the devs/QAs able to successfully discover and understand every interaction?