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>
32 lines
2.6 KiB
JSON
32 lines
2.6 KiB
JSON
{
|
|
"case": "h-web-portal/screens",
|
|
"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,
|
|
"no-history case says so": true,
|
|
"misleading status flagged": true,
|
|
"session re-login limit": true,
|
|
"screenshots folder": true,
|
|
"daily schedule": true
|
|
},
|
|
"cost_usd": 0.6750481999999999,
|
|
"subagents": 0,
|
|
"work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-web-portal-screens-h_bv76e8\\project",
|
|
"reply": "Ops handover doc ready: `HANDOVER.md`, bot repo root-la irukku. Bot-ah run pannala, code, config, README and log mattum padichen.\n\n| Item | Count |\n|---|---|\n| Sections | 13 |\n| Exceptions catalogued | 10 (E01\u2013E10) |\n| Failure classes | 10 covered, 2 not applicable (F8: auto-rerun loop illa; F10: batch/lock illa) |\n| Fix before handover | 12 items |\n\n**Ops-ku mukkiyamaana fix items:**\n- Portal maintenance-la irundha, file illaama green \"Downloaded\"-nu kaatudhu (E05).\n- \"Login Failed\" rows-ku colour fill aagala.\n- Run crash aana, meedhi providers report-la row-ae varaadhu.\n- Late-ah vandha CSV adutha provider kanakkula poidum.\n- Version number engayum illa.\n- Log-la status mattum dhaan, reason illa. Ops-ku logs folder access-um illa.\n- `config.yaml`-la use aagaadha live-looking API token irukku. Adha rotate panni remove pannanum. Value-ah doc-la podala.\n\n**Checks:**\n- PHI, secrets, `{{` placeholders doc-la illa.\n- file:line refs section 13-la mattum dhaan irukku.\n- Ellaa status strings-um Statuses table-la irukku.\n\n**Notes:**\n- `data/downloads` and `data/screens` README-la \"output\"-nu list aagirukku, adhaala adhaiyum ops reach panna mudiyum-nu eduthukitten.\n- Git history illa. Adhaala Known incidents-la log-la irundha 2026-09-02 run oru row mattum dhaan.\n- Bot run pannaama code padichu ezhudhinadhu. Doc innum live run-oda check pannala.\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 whose meaning the code doesn't make clear?",
|
|
"stderr": ""
|
|
} |