Files
Rpa_Skills/skills/rpa-bot-handoff
VasanthandClaude Opus 5.5 f4c42f2956 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>
2026-10-28 15:01:42 +05:30
..

rpa-bot-handoff

A Claude skill that writes the ops guide for an RPA bot that is being handed over to an ops team.

What you get

HANDOVER.md: the ops guide, in plain words, for operators who don't read code:

  1. What this bot does
  2. Where is what: which tab, screen, file or folder shows what
  3. How to run: checklist and steps with the real button names
  4. How long to wait at each step, in seconds or minutes, and when to step in
  5. After the run: what each ending means, where the report is
  6. How to see an exception
  7. Exception list: message → where → meaning → what you do → wait or call us
  8. How you will know something went wrong
  9. How to tell the dev team, with a ready message template
  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

Copy this folder to ~/.claude/skills/rpa-bot-handoff/.

Use

In your bot project, ask Claude: "write the ops guide for this bot" or "document this bot for handover". The skill:

  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
SKILL.md Steps Claude follows
templates/HANDOVER.md The ops guide skeleton
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)