PB-033
Spec Readiness Check
Before you run any spec in this directory, tells you whether your data supports it — and what to fix first.
The spec — copy this
Set up a new bot for me I can trigger against any spec from this directory. Walk me through connecting my case management system, then configure it: read the spec I point it at, extract every field and data condition it depends on — lead source, incident date, jurisdiction, matter type, cost categories, activity timestamps, disposition reasons, whatever the spec names — and check each one against my live system: does a field exist for it, what is its fill rate, how consistent are its values, and how far back does usable history run. Return a verdict in three buckets: ready to run; will run but the output will be unreliable, and here is exactly why; and cannot run until this is fixed. Give the specific remediation for every gap and a rough sense of the effort. Where a spec needs history to mean anything — anything comparing cohorts, trailing medians, or year-over-year — tell me whether I have accumulated enough of it yet, because a correct spec run against four weeks of data produces a confident wrong answer. Never report a spec as ready on the basis that a field exists; existence is not fill rate. Ask me which spec, which system, and my minimum acceptable fill rate, run it against a spec I have already tried so I can compare its verdict to what actually happened, then save it.
Paste into an assistant that can connect to your systems.
Connect first
The spec asks for these as it goes — however you normally connect them works. Nothing needs to be set up in advance, and a system named here is usually an example rather than a requirement. If yours has an API or an export, the spec generally adapts.
What it never does
- Report a spec as ready because a field exists — existence is not fill rate
- Modify any field, record, or configuration
- Judge whether a spec is a good idea for your firm; it judges only whether your data supports it
- Category
- Data Plumbing
- Contributed by
- Jacob Malherbe Mass Tort Ad Agency↗
- Approval gate
- A named human approves before anything sends, files, or publishes.
- Last verified
- 2026-08-19
More in Data Plumbing
-
PB-008
Case Management Field Map◆
Inventories what your system actually stores — real API names, fill rates, and the three places the same value lives.FFilevineLLitifyCCasePeer+1
-
PB-013
Export Cleanup Pipeline◆
Turns a raw export into a validated dataset, with every row it could not clean listed rather than silently dropped.FFilevineLLitifyGSGoogle Sheets+1