Step 4 now gives the exact recipe used for the MEK SOP: Python markdown
(tables + fenced_code, blank line before lists), the page style (A4,
navy/teal headings, light-blue table header, bold E-numbers, rows that
don't split, grey email box), headless Edge/Chrome --print-to-pdf without
header/footer, and a page-by-page look via PyMuPDF images.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SKILL.md step 4 now tells Claude to render the SOP as one styled HTML page
(A4, 1.8 cm margins, 10.5 pt sans, bordered tables with a shaded header,
grey email box) and print it with headless Chrome or Edge, then look at
every page. The skill is one 54-line SKILL.md. Tests updated; the docx
selfcheck test is removed with the converter.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The skill is now one SKILL.md (54 lines) with the SOP shape inline, plus
templates/to_docx.py for the Word and PDF. Removed: the template, the MEK
reference example and the skill README. The converter's selfcheck uses a
built-in sample. Tests now check the skill is that one short file, has the
6 don't-miss checks, and its SOP shape has the 5 sections and To/CC lines.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The skill itself read as too detailed. SKILL.md is now a short checklist
(460 words, was 1,321): 5 steps, 5 rules, and 6 one-line "don't miss"
checks that replace the 12 Tebra failure classes (failure-classes.md
removed). The MEK Charge Reconciliation SOP - the 3-page PDF ops liked -
replaces the Tebra example as the model (emails swapped for examples).
New test keeps SKILL.md under 500 words with 6 checks.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- 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 SOP (MEK Charge Reconciliation, 1,327 words) printed on 5 pages:
Word's 2.5 cm default margins and 10.5 pt table text. to_docx.py now uses
1.8/1.6 cm margins and 9.5 pt table text; the trimmed SOP (1,226 words)
prints on 3 pages. The verify step counts real pages through Word when it
is installed.
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>
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>
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>
Read-only SQL review against 10 rules (SQL Server + pyodbc). The review
runs in a subagent and every issue lands in query_tracker.md with a
before/after fix plan.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
