Of course - but if we want to "force" (do we? How?) user documentation before a feature is developed then without expressing intent of what we want to implement first, it might be extra effort that will be difficult to do.
I never proposed to "force" ADR, I suggested treating it as a good practice. I was even thinking that as a first step of introducing them we could retroactively generate ADRs and first ensure consistency between ADRs and user documentation. Then, we could add agentic instructions to keep these in sync (which is more than possible now). This would be my way of "gently" introducing them rather than forcing. I think this has a chance of working quite naturally. BTW. Do you want to propose a way to "force" users to read the documentation? Or should it just suggest/recommend? What would you suggest there? How would you implement it? I really like the approach of Python PEPs, where mandatory part of any change is "How to teach this?". So... how?
