A similar approach I've been using recently and am so far really, really enjoying is to put all "conversation" into a dedicated "devlog" directory in the projec

A similar approach I've been using recently and am so far really, really enjoying is to put all "conversation" into a dedicated "devlog" directory in the project root. We put everything in it: meeting notes, project status updates, memos, changelogs for every pull request, reviews, etc. Every file is markdown and named with a date prefix, a "nonce" for uniqueness, and a category (date.nonce.category.md). So you might have something like: - 2023-08-10.00.notes.md - 2023-08-10.01.notes.md - 2023-08-11.00.changelog.md - 2023-08-11.01.changelog.md - 2023-08-11.00.review.md - 2023-08-11.01.review.md - 2023-08-11.02.review.md - 2023-08-11.00.project.md The file naming includes a small amount of ambiguity and a small opportunity for merge conflicts but in practice it's just not a problem. The best part of this workflow IMO is that it doesn't create a whole new workflow for communication, it treats high-quality async communication as part of the core (pull, read, commit, push, review) development workflow.