" Are there any other requirements or protocols unique to windows modules? "
Generally if submitting them to core (I don’t understand anyconfig yet so not sure we’d take it), docs go in a corresponding “.py” file (see other windows modules for an example.
But that’s pretty much it - just follow the examples of the others, etc.
Sounds to me like maybe you are after win_copy, win_template and win_lineinfile modules. I have created PRs for the first two.
If you don't mind working from development version of Ansible you could try them now. I'd be grateful for any feedback.
That might get you most of what you need, with the exception of replacing lines in existing files. You might find using the existing lineinfile module as a starting point would be a help. Actually, thinking about it, you might be able to make use of a combination of of fetch, lineinfile and win_copy to manipulate the configuration files, if you can run lineinfile delegated to your Ansible controller, and you can get away with replacing the files on your windows nodes.
Jon
PRs, if you are interested are:
https://github.com/ansible/ansible-modules-core/pull/384
and
https://github.com/ansible/ansible/pull/9611
Jon
A second copy of lineinfile is something I do want to avoid 
The others are good things. We may still look at how to make these share more in common using the ‘v2/’ codetree when that gets closer to completeness.
Thanks!