[spdionis]

Yes. Get a meeting a room and do a proper meeting. The thought of having a 1 hour long meeting makes me sick. The thought of having a 1.5-2 hours long phone call (adjusted for inefficiency of the phone call) makes me want to kill myself. I will not get anything done ever after that.

[Clubber]

The person writing the spec should actually be able to think it through a few times before needing a developer in the room. If the spec writer can't think through a spec by themselves for at least 95% of it, they aren't qualified to be submitting tickets, IMO.

The most efficient way to communicate specs is through a document, so I have something to reference. I'm not going to remember everything said in a meeting unless I immediately start working on it. The spec document should be exhaustive, clear and easy to follow with no dangling questions unanswered.

If you can get a spec writer that can do that, you're golden.

[spdionis]

You have never written a spec have you?

Not only is the 5% important, as every "only 5% left" tends to be, you are completely ignoring possible developer questions.

[Clubber]

I've read my take of shit ones. Most of the time, the writer hasn't bothered to think about it past the initial idea and needs the developer to help them understand what they want. That's not the developer's job.

[spdionis]

Remember this when you'll write your first spec one day.