- Section 5 of the SOP now names a real "To" (the developer) and "CC"
(the developer's manager, not the operator's), and the email block to
copy starts with To: and CC: lines. The skill asks for both addresses.
- to_docx.py --pdf also writes the PDF (Word through PowerShell on Windows,
LibreOffice elsewhere) and prints the real page count against MAX_PAGES.
The PDF is what ops gets.
- Tebra reference and README updated; new test for the To/CC lines.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first real handover (MEK Charge Reconciliation) came out at 9 pages.
Ops want it short: which URL to open and what to click, what shows where
after the click, what to do when an exception comes, and how to email us.
- Output is "<Project Name> Handover SOP" (HANDOVER-SOP.md + .docx) with
5 sections: how to run, what you see while it runs, result, when
something goes wrong, email us. HANDOVER-DEV.md is dropped; dev-team
findings go in the chat.
- At most ~1,400 words; to_docx.py prints the word count and flags overflow,
and renders *italic* for the variable parts of messages.
- Every quoted message, label and URL is checked against the code. The SOP
must say what clicking Run again does to the data.
- One scan subagent; failure classes stay as a scan checklist.
- Tebra reference rewritten in the SOP format; test, README, glossary
updated; ADR-0005 supersedes ADR-0004.
The handoff eval runner (tests/evals/run_handoff_eval.py) still grades an
older 13-section format and was already out of date; not touched here.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>
