When working on a team, the more everybody understands what you're thinking and what you're doing the better. Even when your thoughts seem obvious, there's value in saying them out loud (or the the chat equivalent of out loud). This overcommunication has several benefits.
First, it provides system visibility. If you're launching something big, post a message in a relevant Slack room saying "FYI: Big change in XYZ system going out in 10 minutes!" This way if someone is going to have a conflict or wants to wait because a demo is about to happen they can speak up. Also it means more people are aware of a the change so any issues might be caught faster.
Overcommunicating also provides opportunity for discussion and learning. When you make a point to bring up something in public, it forces you to organize your thoughts clearly and put a stance on a statement. Once you have a clear stance, stated publicly, you can have a real discussion on things rather than just assuming everybody is generally on the same page. Writing design proposals before starting large chunks of work is a great example of this type of discussion-encouraging communication.
Finally, overcommunicating lets people know what you're up to and increases your visibility in the group. This also lets people know what's being worked on and invites collaboration (don't assume everybody has read or remembers all the passive communication like documentation and roadmaps).
You don't want to become noise, make sure you're saying useful things to the right audiences, but particularly in remote situations where a lot of communication happens though text, erring on the side of overcommuncation can be very valuable.
Bonus idea! Automate you're overcommunication by having bots post updates to channels on things like deploys and system status changes.