For work projects, I often write a short README file first, and share it with my team as a sanity check before writing a single line of code. It's just rough d

For work projects, I often write a short README file first, and share it with my team as a sanity check before writing a single line of code. It's just rough draft which says "here is the problem I think we are solving, and why/how we're solving it". If my team has feedback, I update the README. This is easier to keep track of than Slack conversations. If necessary, this document can be polished later, when other people need to use the thing we built. But it's nice to have a starting point.