rpa-bot-handoff: end with HANDOVER.docx for the ops team

New last step: templates/to_docx.py turns the finished HANDOVER.md into a
Word document (python-docx), the skill checks it and gives that path to
the user as the deliverable. --selfcheck converts the Tebra example and
is run by tests/test_templates.py.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

skills/rpa-bot-handoff/README.md

@@ -16,6 +16,8 @@ A Claude skill that writes the **ops guide** for an RPA bot that is being handed
 10. Don'ts, and the right way to stop the bot
 11. Issues seen before
 
+**`HANDOVER.docx`**: the same ops guide as a Word document. This is what you give the ops team at the end.
+
 **`HANDOVER-DEV.md`**: for developers. The check against 12 failure classes learned from Tebra Auto Post, the gaps to fix before handover (file:line), and the incident list.
 
 ## Install
@@ -26,6 +28,7 @@ In your bot project, ask Claude: *"write the ops guide for this bot"* or *"docum
 1. Scans the code and history with subagents. It never runs the bot.
 2. Asks up to three things: how ops reaches the dev team, what ops can open, and any unclear statuses.
 3. Writes both files and checks them.
+4. Turns the ops guide into `HANDOVER.docx` and gives you that document to hand to ops.
 
 ## Files
 | File | What it is |
@@ -35,3 +38,4 @@ In your bot project, ask Claude: *"write the ops guide for this bot"* or *"docum
 | `templates/HANDOVER-DEV.md` | The dev notes skeleton |
 | `templates/failure-classes.md` | 12 failure classes from Tebra's first months with ops |
 | `templates/reference/tebra-auto-post.md` | Both files filled in for Tebra, scrubbed |
+| `templates/to_docx.py` | Turns `HANDOVER.md` into `HANDOVER.docx` (`--selfcheck` tests it) |