As mentioned by Tony and adrianh already, the best way would be to get everybody together to do a kickoff and discuss the requirements.
If this is difficult to do because people belong to different teams, then request your requirements to be delivered as a single versioned document.
E.g.
- Doc starts as out with just the wireframe
- Interaction Designer annotates the doc with interaction notes. If certain behaviour are too difficult to describe in words, reference to a prototype
- Copy writer also annotates the doc (use a different color/symbol if you'd like) e.g. "C-1.1" over content elements, and again referenced to the relevant section in their word doc
- Visual Designer then replaces/overlays the page mockups on top of the wireframe. Make sure all the annotations are brought over during the process
- Each time an update is made, track it as a new version and a quick message should be sent to these 3 people so they can quickly scan to make sure everything still make sense after the change.

download bmml source – Wireframes created with Balsamiq Mockups
Note:
Having a commonly available and easily editable document is key in making sure things remain up to date. I prefer something like Omnigraffle for this from the sense that you can have multiple pages within the doc for various screens, layers on a page for annotation vs mock, easy copying and pasting of images & text and quick export out to PDF for easy sharing. (There's probably other tools out there with similar functionalities)