[tmaly]

I have to deal with this same issue on a daily basis. I agree with others that you have to make the documentation task part of the process.

I have Confluence templates for business requirement documents and technical specification documents. These always get jira tasks for any new project.

It is always a challenge to get the business side to write proper requirements. This is where a good business analyst can come in.

In lieu of that, I think having a developer gather requirements in the form of use cases and documenting them with the Gherkin format is tradeoff I will accept. These use cases as acceptance tests can easily sit in a text file along with the code.