It absolutely is, and I think it's what separates good from bad and junior from senior devs.
Most devs can produce an artifact that more or less works. But one that has an internal consistency others can understand and extend, one which accurately captures the problem as it exists and ways it will likely change, is much more of an art form.
A big part of that is knowing which situations are worth making a stand. Every you write code or leave feedback, your doing it for your team current and future.