Skip to content
discovery-dispute-letter logo

Discovery Dispute Resolution Letter

discovery-dispute-letter

Drafts discovery dispute resolution letters documenting meet-and-confer efforts and unresolved issues in U.S. litigation. Use when drafting meet-and-confer letters, discovery conference follow-ups, or pre-motion to compel correspondence during the discovery phase.

CaseMark/skills0installs44starsOther

SKILL.md

Full skill instructions

Discovery Dispute Resolution Letter

Drafts a court-ready letter that documents meet-and-confer efforts, memorializes agreements, and builds the record for potential motions to compel.

Required Inputs

  1. Case info — caption, court, case number, judge, discovery deadline
  2. Conference details — date, participants, outcomes (if conference held)
  3. Disputed requests — exact request language, objections raised, compromises discussed
  4. Scheduling order — discovery cut-off, motion deadlines

Letter Structure

Header: Date, opposing counsel address, Re line with full caption, case number, client name, matter number, discovery cut-off date. Include "Via Email" with address.

Body sections in order:

  1. Opening — Reference conference date/​participants, acknowledge agreements, identify remaining disputes. Note motion practice may follow.
  2. Agreements Reached — Numbered list of compromises with compliance deadlines. Request written confirmation.
  3. Outstanding Disputes — Organized by discovery method (RFPs, interrogatories, depositions). Use the per-dispute format below.
  4. Deadlines — Specific response date tied to court schedule. State motion to compel and sanctions consequences.
  5. Closing — Invite further discussion, propose specific follow-up date/​time. Include preservation reminder.
  6. Signature Block — Name, title, contact info, cc list, attachments (original requests, conference notes, scheduling order).

Per-Dispute Format

Each disputed item must include all four elements:

  1. Exact Request Language — quote verbatim as served
  2. Opposing Objection — quote verbatim
  3. Why Objection Lacks Merit — cite applicable rules and authority
  4. Proposed Compromise — narrowed alternative demonstrating reasonableness

Letter Type Variations

  • Pre-conference agenda — collaborative tone; outlines issues for conferral; sent before meet-and-confer
  • Post-conference follow-up — precise, collaborative; memorializes agreements, narrows disputes; sent within 24–48 hours
  • Pre-motion to compel — firm, formal; final attempt before court involvement; allow response time before filing deadline

Guidelines

  • Write for the judge — every sentence may become a motion exhibit; make the client look reasonable
  • Quote exactly — requests and objections must be verbatim as served
  • Characterize fairly — describe opposing responses accurately even when inadequate
  • Cite authority — FRCP 26(b)(1) (proportionality), FRCP 30(a)(1) (depositions), FRCP 33(d) (interrogatories), plus local rules
  • Demonstrate good faith — show willingness to compromise on scope, timing, or format
  • Pin down follow-up — always propose a specific callback date/​time to prevent indefinite delay
  • Preservation language — remind of ongoing duty to preserve documents and ESI

Court-Specific Notes

  • Federal — Rule 26(f) meet-and-confer required; Rule 26(b)(1) proportionality; magistrate referral; CMO deadlines
  • State — verify local meet-and-confer requirements; check objection standards and discovery cut-off calculations
  • Complex commercial — address e-discovery protocols, protective orders, voluminous production, privilege log disputes

Checklist

  • Local meet-and-confer rules satisfied
  • Reasonable response deadline provided
  • All disputed items identified with exact request language
  • Good faith compromise demonstrated for each dispute
  • Legal authority cited for contested positions
  • Firm but professional tone throughout
  • Preservation language included
  • Letter is court-exhibit ready

More Other skills

Delegate independent tasks to specialized agents working concurrently with isolated context.

295.4K 206.3K
View

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

179.7K 100.1K
View

Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.

179.7K 89.5K
View

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

179.7K 76.1K
View

Fundamental design principles for writing maintainable, testable Python code.

40.2K 21.9K
View

Modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first strategies.

40.2K 20K
View

Generate Playwright tests from scenarios using interactive browser exploration and validation.

39.7K 18.2K
View

Modern React state management with Redux Toolkit, Zustand, Jotai, and React Query for every state category.

40.2K 14.7K
View

GDPR-compliant data handling with consent management, data subject rights, and privacy controls.

40.2K 14.3K
View

Python error handling patterns including input validation, exception hierarchies, and partial failure handling. Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs.

40.2K 13.5K
View

Detailed multi-file refactor planning with safety checks and rollback guidance.

39.7K 13K
View