| name | discovery-separate-statement |
| title | California Discovery Separate Statement |
| description | Drafts a California-compliant discovery Separate Statement for motions to compel under Cal. Rules of Court rule 3.1345. Trigger when the user mentions a California motion to compel, Separate Statement, "sep stat," Rule 3.1345, CCP 2023.030 sanctions, interrogatory/RFP/RFA/deposition disputes, or verbatim request-response formatting for CA Superior Court discovery motions. |
| author | CaseMark |
| author_url | https://github.com/CaseMark/skills/tree/main/skills/legal/discovery-separate-statement |
| license | Apache-2.0 |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | us |
| practice | litigation |
| language | en |
| tags | ["drafting","motion"] |
California Discovery Separate Statement
Produces a request-by-request Separate Statement that is verbatim-accurate and aligned with the motion package (memorandum, declaration, proposed order). Required under Cal. R. Ct. 3.1345 — omission renders the motion procedurally defective.
Quick Start
- Collect verbatim request/response text and meet-and-confer record
- Build a disputed-item ledger locking sources
- Draft per-item blocks (request → response → meet-and-confer → reasons → remedy)
- Run consistency pass against the full motion package
- Deliver for attorney review
Pre-Draft Intake
Gather before drafting (apply labeled defaults if user says "use defaults" or "just draft"):
- Discovery set — verbatim propounding text, definitions, latest responses (objections, qualifications, verification status, production references)
- Meet-and-confer record — letters, emails, declarations with dates; concessions or supplements
- Case framing — complaint/answer (claims, defenses tied to each request); protective orders, ESI protocols
- Motion posture — motion type, proposed relief, hearing date, 45-day deadline calculation including service method
- Court requirements — local/department preferences (IDC/JCCP, format, tables vs. sequential text)
Defaults if user skips: compel further responses; all disputed requests; sequential text; sanctions under CCP § 2023.030.
Hard stop: If verbatim request/response text is missing, halt and request it before drafting.
Core Workflow
1. Classify Motion
Produce a single-line taxonomy and gap check:
Taxonomy: Motion to compel further responses to [device/set]: Nos. [range], plus [relief/sanctions].
- Further-response motion with deficient responses → Separate Statement required (Cal. R. Ct. 3.1345(a)) [VERIFY]
- Pure failure-to-respond → may use alternate CCP tracks [VERIFY]
2. Build Disputed-Item Ledger
One row per disputed item — source-lock table preventing drift:
| Item ID | Device | Request Source | Response Source | Service Date | Dispute Type |
|---|
| RFA-1-8 | RFA | RFA Set One No. 8 | Response 3/01/2026 | 3/01/2026 |
