A model can produce a plausible procedure from a schema and a changelog. What it cannot do is decide which procedure matters, notice that the schema contradicts the deployed behaviour, or sit with an engineer until the actual constraint surfaces. Those were always the expensive parts. They are now the only parts.
The writers who come out ahead are the ones who move up a layer. Own the information architecture, not the paragraph. Own the style guide that makes fifty pages read as one voice. Own the review loop that catches the wrong claim before a customer builds on it. Set up the templates and the checks, then let the machine fill them.
This also raises the floor on accuracy. Text that is cheap to produce is cheap to produce wrongly, at volume. Someone has to be accountable for whether the documentation is true. That accountability does not automate.
The craft is not disappearing. It is moving from writing sentences to designing the system that produces them, and then guaranteeing the result.