Another approach is to write the spec while refactoring the reference implementation into something more documentable. Any superfluous functionality than can be removed from bitcoind and moved to the clients is less functionality a fully-compliant alternate implementation is required to implement.
Yes, but the disadvantage of that method is the (possible? probable?) leak of things that don't belong into the spec draft. In general doing multiple things at the time should be avoided as much as possible.