Lawyer Case File Archiver

Problem

Civil case files often become hard to archive because materials are scattered, firm templates define different fields, and Word table positions are unstable. Manual completion can miss authorization materials, or mix mutually exclusive case materials into one volume.

How It Works

The skill runs with a generic engine plus law-firm configuration outside the package. It reads paths, archive_plan, field_map, and preferences, scans the file tree, and extracts text from PDF, DOCX, DOC, and permitted scanned images. Core actions include archiving existing materials, updating completion status, onboarding new templates, checking Word templates, and merging PDFs only after explicit user confirmation.
DOCX filling prefers stable locators such as marker, control_tag, and cell_anchor, with strict mode enabled by default. Missing fields, non-unique labels, or failed post-write validation preserve the original output and record the reason in fill_report. It generates an archive-status JSON file and a pending-materials list, marking missing materials as pending and positioning failures as error. For individual or organizational clients, it checks required materials such as ID documents, powers of attorney, firm letters, and lawyer licenses, and records missing items in the pending list.

Boundaries And Notes

It is suitable for partial archiving of open cases, but not for unconfirmed automatic PDF merging. Before formal use, run a masked dry trial and check fill_report.errors, the pending list, and the rendered DOCX layout. Low-confidence mappings, merged cells, and repeated labels require human review.