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/SKILL.md

@@ -15,6 +15,7 @@ Write two files in the bot's repo:
 | `templates/HANDOVER-DEV.md` | The dev notes skeleton. |
 | `templates/failure-classes.md` | 12 failure classes from Tebra Auto Post. Every one must be checked against the bot. |
 | `templates/reference/tebra-auto-post.md` | A filled example of both files for Tebra, scrubbed. Copy its depth and wording, not its content. |
+| `templates/to_docx.py` | Turns the finished `HANDOVER.md` into `HANDOVER.docx`, the document handed to ops. Needs `python-docx`. |
 
 Rules:
 - **Never run the bot.** Real bots act on live systems. Read code, config, logs and history only.
@@ -22,7 +23,7 @@ Rules:
 - **Every wait is a number.** Take timeouts, retries and watchdog limits from the code, in seconds or minutes. Take normal durations from the logs when they show them; otherwise write "not measured".
 - **Write what the code does, not what it should do.** If a status is misleading (an item needing follow-up shows green), say so plainly in the ops guide and add it to the gaps in `HANDOVER-DEV.md`.
 - **Never copy** patient data (PHI), customer names, credentials, internal IPs, keys or `.env` values into either file. Logs are read for message types and durations only.
-- Change no code. The only output is the two files.
+- Change no code. The only output is the two files and `HANDOVER.docx`, the Word copy of the ops guide that is handed to ops at the end.
 
 ## 1. Scan (subagents are required)
 
@@ -86,4 +87,11 @@ Copy `templates/HANDOVER-DEV.md` and fill it:
 4. Search both files for PHI, customer names, credentials, IPs, keys and `.env` values. There must be none.
 5. The ops guide has no file:line, class or function names, or SQL.
 6. `HANDOVER-DEV.md` accounts for all of F1-F12.
-7. Report to the user: sections filled, number of exceptions listed, failure classes covered vs not applicable, and the gaps for the dev team.
+
+## 6. Hand over the document
+
+The skill always ends with one document the user can give to ops.
+1. Run `python <skill>/templates/to_docx.py HANDOVER.md`. It writes `HANDOVER.docx` next to it. If `python-docx` is missing, run `pip install python-docx` first. If that is not allowed, say so and hand over `HANDOVER.md` instead.
+2. Open the `.docx` with python-docx and check that it has 11 numbered section headings and that no `**` or `|---` is left in its text.
+3. Give the user the path to `HANDOVER.docx` as the deliverable: "Give this to the ops team." `HANDOVER-DEV.md` stays in the repo for developers and is not handed to ops.
+4. Report: sections filled, number of exceptions listed, failure classes covered vs not applicable, and the gaps for the dev team.