This is good thinking, and you may still want something like this anyway, as there's always room for additional documentation, but let me propose an alternative that takes this good way of thinking a step further:
Infrastructure-as-code means my code is my documentation. How's it configured? Look at the code. What's it doing? Look at the code. Don't understand why it's doing that? Use more descriptive names for things and write more self-explanatory code. Is the code out of date with the current state? Stop implementing things manually and make the code run automatically instead so it's never out of date anymore.
I have complete confidence in my setup and life is easy now. Except when the IAC breaks. But that's rarely a panic situation, just mildly frustrating.
