VasanthandClaude Opus 5.5
3942fad6cd
The skill scans a bot with subagents (never runs it) and writes HANDOVER.md, an 11-section ops guide in the operator's order: where is what, how to run, how long to wait, after the run, how to see an exception, exception list, how you will know, how to tell us, don'ts, issues seen before. Dev material (check against 12 failure classes from Tebra Auto Post, gaps with file:line, incidents) goes to HANDOVER-DEV.md. Also adds ADR-0004, glossary terms, five fixture bots and a handoff eval runner (--resume, --regrade) with results from 47 runs of the earlier 13-section version. The grader still expects that structure and must be updated before the next eval run. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
38 lines
1.7 KiB
Markdown
38 lines
1.7 KiB
Markdown
# 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-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.
|
|
|
|
## 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 |
|