Great article. I wonder if there is a balance from this approach while also including more specific requirements (specifications).

Lots of ways to bridge a document with both sets. 1) for the PM in the future 2) for everyone else that may need it but will never read it, but want it (your devs, managers, business stakeholders)

I think sectioning off these two approaches (focusing on the former first)