Identify Issues In Discovery Responses

---
name: identify-issues-in-discovery-responses
task_id: trusts-estates-private-client/identify-issues-in-discovery-responses
description: Closes the gap where agents identify discovery deficiencies without computing procedural deadlines and waiver consequences, quantifying the impact of omissions, connecting suspicious transfers to dissipation, and flagging sworn declaration arithmetic errors.
activates_for: [planner, solver, checker]
---

# Skill: Identify Issues in Discovery Responses — Deficiency Memorandum

## 1. Subject-matter triage (only if applicable)

- This skill applies when you are comparing an opposing party’s discovery responses against a client record set, temporary orders, and related financial documents to support a compel or sanctions motion.
- First identify whether the response set includes multiple interrogatories, requests for production, or sworn financial statements; if so, treat each request, time period, and asset category as a separate issue lane.
- If the source set contains a discovery cover letter, response dates, extension correspondence, temporary orders, and financial records, use them as the primary chronology before drawing any defect conclusions.

## 2. Failure modes the skill is correcting

- Treating discovery as “substantially complete” when the response was late and no valid extension or order appears in the record; the timing defect may support waiver of objections and motion practice.
- Missing omissions where an asset, entity, account, property, or transfer appears in one document but disappears from the response to a broader request.
- Failing to flag that a response narrows a request beyond its stated scope, especially where the request reaches assets held directly or through controlled entities.
- Overlooking sworn declaration errors, including duplicated liabilities, inconsistent net-worth math, or missing verification defects.
- Accepting privilege objections that are conclusory or that attach to ordinary financial records rather than protected communications.
- Ignoring suspicious timing between a claimed debt, a related-entity transfer, and the separation date, which can support dissipation or fabrication arguments.
- Failing to tie each deficiency to the client-side consequence, such as incomplete asset tracing, impaired support calculations, sanctions exposure, or an evidentiary basis for compel relief.

## 3. Legal frameworks / domain conventions that apply

- Discovery timing and waiver: apply the governing civil procedure rule for response deadlines, extensions, and objection waiver; if responses are served after the deadline without agreement or court authorization, analyze waiver and compel consequences under the applicable rule.
- Scope interpretation: interrogatories and document requests that ask for property, accounts, or entities “directly or indirectly,” “individually or through any entity,” or similar language require disclosure of controlled entities and indirect holdings.
- Privilege doctrine: attorney-client privilege generally protects confidential legal communications, not underlying financial records, business records, or materials merely routed through counsel; work-product protection turns on litigation anticipation and the nature of the document.
- Financial declaration accuracy: sworn financial statements must be complete and internally consistent; duplicate treatment of a liability or inconsistent asset valuation should be treated as a material defect.
- Oath/verification requirements: confirm whether the sworn statement satisfies the forum’s verification, notarization, or declaration requirements before relying on it as competent disclosure.
- Dissipation analysis: compare suspicious transfers, related-party obligations, and post-separation account activity against the timeline and source records to evaluate whether funds were moved, concealed, or recast as liabilities.
- Temporary orders: any court-ordered disclosure obligations, accounting requirements, or preservation directives supplement ordinary discovery obligations and should be cited as independent support for compel/sanctions relief.

## 4. Analytical scaffolds

1. Build a chronology of service, due dates, any extension requests, any written agreements, and actual service dates; determine whether objections are arguably waived and what relief that timing defect supports.
2. For each interrogatory and request, compare the response to client records, prior disclosures, account statements, tax documents, title records, and temporary orders; identify every inconsistency, omission, narrowing move, or unsupported denial.
3. For entity-ownership and property requests, enumerate the entities, accounts, properties, and interests appearing in the source set; then test each item against the response to see whether it was omitted, misdescribed, or disclosed only in part.
4. For privilege objections, isolate the withheld category, the asserted privilege, and the document’s actual nature; flag objections that do not match the governing privilege standard or that omit a privilege log basis.
5. For sworn financial declarations, reconcile each asset, liability, and net-worth component against underlying records; check for double-counting, missing liabilities, stale values, and arithmetic drift.
6. For suspicious-liability or transfer issues, pair the claimed obligation with the related-party transfer history and the separation timeline; assess whether the documents support a bona fide debt, dissipation, or concealment narrative.
7. For each defect, state: the exact response problem, the source document contradiction, the governing rule or doctrine, the magnitude or practical effect if determinable, and the requested corrective action.

## 5. Vertical / structural / temporal relationships (only if applicable)

- The discovery response date controls the timing analysis; the cover letter or proof of service is the anchor for calculating lateness.
- Temporary orders may impose broader disclosure or preservation duties than the baseline discovery requests; cite them separately when they expand the obligation.
- Source documents should be read in sequence: request, response, objections, verification, privilege log, financial statement, bank records, title records, and then any later supplementation.
- A later disclosure can sometimes confirm an earlier omission; do not treat later production as curing all defects unless the record actually shows full supplementation.

## 6. Output structure conventions

- Use a memorandum format with an opening summary, a severity key, issue-by-issue analysis, and a final recommended actions section.
- Define a uniform ordinal severity scale at the top, then assign a severity label to every issue.
- For each issue, include:
  - severity
  - request/response at issue
  - source basis from client records or temporary orders
  - controlling rule, doctrine, or authority
  - analysis of the defect
  - practical consequence for compel/sanctions strategy
  - recommended corrective action
- When there are multiple discovery requests, entities, properties, accounts, or periods at issue, enumerate them separately rather than collapsing them into one generalized observation.
- Quantify the issue where the record allows it by tying it to the relevant date, account balance, asset category, number of omissions, or amount at stake without inventing unsupported arithmetic.
- If a legal proposition is stated, identify the governing authority by name and section/rule when available, and do not state conclusions without the supporting rule.
- End with a concise Recommended Actions block that tells counsel what to move for, what records to demand, and what follow-up deadlines or hearing dates should drive next steps.