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>
31 lines
2.4 KiB
JSON
31 lines
2.4 KiB
JSON
{
|
|
"case": "h-mail-intake/full",
|
|
"rep": 4,
|
|
"passed": false,
|
|
"checks": {
|
|
"HANDOVER.md written": true,
|
|
"no other file changed": true,
|
|
"bot never run": true,
|
|
"no placeholders left": true,
|
|
"13 sections in order": true,
|
|
"used subagents": false,
|
|
"every status listed": true,
|
|
"catalogue: 4+ complete rows": true,
|
|
"F1-F12 all accounted for": true,
|
|
"no code refs in ops sections": true,
|
|
"fix-before-handover has file refs": true,
|
|
"no secrets or personal data": true,
|
|
"where-to-look respects ops access": true,
|
|
"asks escalation": true,
|
|
"asks ops access": true,
|
|
"known incidents from history": true,
|
|
"misleading status flagged": true,
|
|
"stuck Processing item blocks the queue": true,
|
|
"20 MB limit": true
|
|
},
|
|
"cost_usd": 0.7672178000000001,
|
|
"subagents": 0,
|
|
"work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-mail-intake-full-m22iw_c5\\project",
|
|
"reply": "`HANDOVER.md` ready \u2014 repo root-la irukku (`HANDOVER.md`). Only that file create pannen; code edhuvum change pannala, bot-ah run pannala.\n\n| Check | Result |\n|---|---|\n| Sections | 13 (template order apdiye) |\n| Exceptions | 10 (E01\u2013E10) |\n| Failure classes | 11 covered, F2 not applicable (desktop window edhuvum drive pannala) |\n| Statuses | 5 status, 6 status+note combo, ellaam listed |\n| Fix before handover | 15 items |\n\n- **Mukkiyamaana vishayam:** 3 \"fix\" commits-um code-la oru comment mattum add pannudhu. Behaviour maaravae illa, so moonu incident-um innum nadakkalam.\n- Stuck \"Processing\" item vandhaa, adhukku appuram ella run-um stop aagidum. Ops-ku DB access illa, so idhu ippo Dev escalation (E02).\n- Encrypted PDF \"Done\"-nu kaattum, aana share folder-ku copy aagaadhu (E04).\n- Unga answers use pannen: escalation #rpa-support; ops-ku log folder + share folder mattum, DB illa; unclear statuses code-la irundhu purinjukitten.\n- Repo chinnadhu (oru ~90-line file), so scan-ku subagents anuppaama naanae padichen.\n- Verify check-la PHI / credential / IP edhuvum doc-la illa. Aana `logs/intake.log`-la oru sender email address irukku; adha doc-la copy pannala (Fix #14).\n\nQUESTIONS: Escalation: who does ops call for a dev issue (team or role), and how (ticket, chat channel)? | Ops access: which of the bot's places can ops open - the app's screens, the output folder, the log folder, the database? | Unknowns: what do the statuses or exceptions mean where the code doesn't make it clear?",
|
|
"stderr": ""
|
|
} |