That feels like, more, using the wrong tool for the wrong job though. Repos do have sweet spots when it comes to huge, deeply nested structures of code where you probably will have changes that span multiple files in multiple places yet just make sense when applied together. Keeping something such as specification documents in a repo ... seems okay'ish but not the best choice for sure.