Are specs missing? Should be painless?

Year after year, company after company, manager after manager and i can count with my fingers where the best design/specs were founded. Mostly of the times i hear "we are agile" and "client first". After a while and legacy starts to grow and those things that could be thought, design and discussed for better solution starts to be pain in the ass. Manager just write long stories that almost are epics, covering lot of functionalities and write fast and short, and once again "agile, first client then we document or find better solution, let's make money". Sure no problem, but one day we will chase the damage in a vicious circle.

With this in mind founded great articles about this subject, like mitical Joe Spolsky and start to first check if this could be a necessity or even a trending search on google.

As introduced on print seems a subject that keeps trending on time.

Could a webapp, help on this? Imagine having your project specs, where you define goals, non-goals, scenarios, epics, overview, authors, by project for organisations and so one, lot of features could popit from this... (jira export, what else, export beauty docs, pdf)..

Would you think this would be a niche, where seems only exist some kind of template docs? What's your opinion indies (devs, designers, managers, cto etc).

I can have garante that if a company culture is not alined with spec first this is not for them, but others that have learn that they won when they first spec/design functional-technical, could it be a product?