Adam, that's a good point. Keeping the questions and their answers in the specification makes it a living reference instead of something everyone read once and then worked from memory.

I've also found that many code review discussions aren't really about code. They're about intent that was never made explicit.

Most of the review arguments I've sat through were two people discovering they'd assumed different requirements, so settling that in the spec first has cut most of them off. I've written up how I approach it here: https://prickles.org/tenet/spec-first-execution/P2