The descriptions of Spec-Driven development that I have seen emphasize writing the whole specification before implementation. This encodes the (to me bizarre) assumption that you aren’t going to learn anything during implementation that would change the specification. Kent Beck puts it well:

I’ve heard this story so many times told so many ways by well-meaning folks—if only we could get the specification “right”, the rest of this would be easy.