Identify Issues In Counterparty Discovery Requests

---
name: identify-issues-counterparty-discovery-requests
task_id: intellectual-property/identify-issues-in-counterparty-discovery-requests
description: Reviewing opposing party discovery requests in an IP litigation matter to identify objectionable requests and develop response strategies, using the pleadings, scheduling materials, and any discovery-related orders to frame scope and objections.
activates_for: [planner, solver, checker]
---

# Skill: Identify Issues in Counterparty Discovery Requests

## 1. Subject-matter triage
- Start by mapping the pleaded patent claims, defenses, accused products or processes, and any discovery orders or scheduling limits that define scope.
- Separate interrogatories, requests for production, and any requests touching source code, technical schematics, commercial data, licensing, or settlement-sensitive material.
- If multiple request sets, custodians, time periods, or product families are in play, enumerate them before analyzing objections so each can be addressed on its own terms.
- Treat the requested memo as an advisory issue-spotting product: identify objections, assess response posture, and flag any protocol or protective-order needs.

## 2. Failure modes the skill is correcting
- Reviewing requests without anchoring them to the pleadings, scheduling order, and discovery-specific rulings that define relevance and limits
- Treating “objectionable” as the end of the analysis instead of pairing each objection with a response strategy
- Missing compound interrogatories, overbroad custodial or temporal scope, or demands for legal conclusions
- Failing to distinguish between full withholding, partial production, and production subject to objection
- Overlooking privileged material, work product, common-interest or joint-defense issues, and the resulting privilege-log duties
- Under-addressing technical, proprietary, or source-code material that requires a confidentiality protocol or controlled review
- Writing generic objections that do not tie the objection to a governing rule, order, or doctrine

## 3. Legal frameworks / domain conventions that apply
- Civil discovery is framed by relevance, proportionality, and the scope set by the pleadings and court orders; requests outside that frame are objectionable under the governing civil procedure rules.
- Interrogatories may be objectionable if compound, unduly burdensome, outside numerical limits in the governing order, or if they seek legal analysis rather than facts.
- Requests for production may be objectionable if they are overbroad in subject matter, time, source, custodian, or electronic search terms, or if they seek categories untethered to the asserted claims and defenses.
- Privilege principles bar disclosure of attorney-client communications and attorney work product; withholding on those grounds typically requires a privilege log sufficient to identify the material, the privilege asserted, and the basis for the claim.
- Common-interest or joint-defense doctrine may protect aligned-party communications where the doctrine applies under the governing jurisdiction.
- Technical or proprietary information can justify a protective order, tiered confidentiality designations, restricted access, and, for source code or similarly sensitive materials, a secure review protocol.
- If the source materials identify controlling authority, cite it expressly; otherwise rely on the applicable discovery rules, protective-order doctrine, privilege principles, and the court’s scheduling framework.

## 4. Analytical scaffolds
1. Identify the universe of request types and any governing limits, then note whether the dispute is request-specific or driven by a broader protective issue.
2. For each interrogatory, test for compound structure, legal-conclusion demand, burden, overbreadth, and any inconsistency with court-ordered limits.
3. For each document request, test for relevance, proportionality, temporal breadth, custodial breadth, subject-matter breadth, and technology-specific sensitivity.
4. For each objectionable item, determine the best response posture: object and withhold, object and produce in part, object and produce subject to a confidentiality regime, or respond fully.
5. For each privilege-sensitive item, identify the privilege or protection implicated and note the need for a privilege log or related disclosure protocol.
6. For each sensitive technical or source-code request, specify the production conditions that would make disclosure workable, including access controls and use restrictions.
7. When drafting the memo entry for an issue, close it with: the scale of the issue as reflected in the source materials, the cross-reference that shows why the request is problematic in context, and the practical consequence for the responding party.
8. Convert each legal objection into a named authority or doctrine rather than a bare conclusion.

## 5. Vertical / structural / temporal relationships
- The pleadings define the claim and defense universe; discovery that reaches outside those boundaries is more vulnerable to relevance and proportionality objections.
- Scheduling orders, ESI protocols, and discovery-specific rulings can narrow custodians, date ranges, topics, and search methodology; those controls should be used to test every request.
- Requests that span multiple products, business units, or time periods should be broken down to determine whether a narrower partial response is appropriate.
- Where technically sensitive material is requested, the relationship between ordinary document production and controlled review matters: access limitations, no-download rules, clean-room review, or staged disclosure may be necessary.

## 6. Output structure conventions
- Organize the memo by request type, then by individual request number or topic.
- Begin with a short severity legend using an ordinal scale and apply it consistently to each issue entry.
- For each objectionable request, include: the request identifier or paraphrase, the severity level, the governing basis for objection, the specific objection language, and the recommended response strategy.
- State whether the response should be full production, partial production, production subject to objection, or withholding pending further protection.
- For each privilege issue, include the related log obligation and any communication categories that may be covered by privilege or common-interest protection.
- For each sensitive technical or source-code issue, add a discrete protocol section proposing confidentiality restrictions, review conditions, or protective-order language.
- End with a Recommended Actions block that gives imperative next steps, assigns them to counsel or the relevant business owner, and ties them to the response deadline or the nearest litigation milestone.