Legal Due Diligence Document Review with Claude Code: Result JSON Schema
A production playbook for legal due diligence document review in legal operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.
Audience: M&A legal teams and diligence operators
The problem
M&A legal teams and diligence operators need legal due diligence document review to run repeatedly against data room folders, contracts, corporate docs, schedules, and exception lists. In legal operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Define the outer result contract once, let the legal due diligence document review skill own body.data, and reject terminal output that does not match the expected schema.
Tradeoffs and failure modes
Schema enforcement adds upfront design work, but removes prompt parsing from the product surface. For legal due diligence document review, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Result shape
{
"schema_version": "argo.result.v1",
"summary": "legal due diligence document review completed",
"body": { "type": "legal_due_diligence", "data": {}, "exceptions": [] },
"artifacts": []
}
Run this on Argo