Disclosure Lazy Financial Custom Report Auto-Fill

Problem

Financial custom reports often mix trial balance sheets, business data, scanned PDFs, and Excel templates. Fillers must repeatedly confirm field sources, debit/credit directions, totals, and period conventions. Manual copying is slow, and the mapping rules often remain in chat history or sheet notes, so similar reports require re-derivation later.

How It Works

The skill constrains the workflow with a report signature + rule base model:
- Identify the report first: read reference docs, extract source fields and template fields, and match an existing report signature.
- Solidify rules next: infer mappings from field names and accounting knowledge, then store confirmed rules with rule_store.py in ~/.workbuddy/report_rules/rules_db.json.
- Validate before filling: run a rule coverage check, preview extracted values, and generate the output with fill_report.py; direct cell edits that bypass the rule base are not allowed.

Boundaries

It fits structured financial templates with recognizable fields, such as balance sheets, income statements, and trial balances. If data is fully unstructured or template fields cannot be identified, manual field cleanup is needed first. The skill enforces rules first: stop and complete rules when coverage is missing, rules are not stored, or preview is not confirmed.