discovery-and-bill-of-particulars
Drafts a combined Demand for Discovery and Bill of Particulars for U.S. criminal or civil litigation. Extracts case details, identifies underspecified allegations or evidence gaps, and produces numbered discovery requests paired with particularization demands. Use after initial pleadings or return date when charges or claims lack specificity, evidence is opaque, or trial-preparation disclosures are incomplete. Trigger keywords include discovery demand, bill of particulars, motion to compel, FRCP 16, FRCP 26, FRCP 33, FRCP 34, FRCP 37, particularity.
Best use case
discovery-and-bill-of-particulars is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Drafts a combined Demand for Discovery and Bill of Particulars for U.S. criminal or civil litigation. Extracts case details, identifies underspecified allegations or evidence gaps, and produces numbered discovery requests paired with particularization demands. Use after initial pleadings or return date when charges or claims lack specificity, evidence is opaque, or trial-preparation disclosures are incomplete. Trigger keywords include discovery demand, bill of particulars, motion to compel, FRCP 16, FRCP 26, FRCP 33, FRCP 34, FRCP 37, particularity.
Teams using discovery-and-bill-of-particulars should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/discovery-and-bill-of-particulars/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How discovery-and-bill-of-particulars Compares
| Feature / Agent | discovery-and-bill-of-particulars | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Drafts a combined Demand for Discovery and Bill of Particulars for U.S. criminal or civil litigation. Extracts case details, identifies underspecified allegations or evidence gaps, and produces numbered discovery requests paired with particularization demands. Use after initial pleadings or return date when charges or claims lack specificity, evidence is opaque, or trial-preparation disclosures are incomplete. Trigger keywords include discovery demand, bill of particulars, motion to compel, FRCP 16, FRCP 26, FRCP 33, FRCP 34, FRCP 37, particularity.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Demand for Discovery and Bill of Particulars Drafts a court-ready pleading combining targeted discovery demands with a bill of particulars to force disclosure, narrow vague theories, and preserve an enforceable compliance record. ## Prerequisites 1. **Jurisdiction and court** — court, division/department, case number, local rules, standing filing/formatting orders 2. **Case posture** — criminal, civil, or hybrid; current procedural stage 3. **Case file** — charging document or complaint, prior pleadings, motions, stipulations, existing discovery responses 4. **Information gaps** — ambiguous allegations or missing disclosures blocking trial preparation 5. **Privilege constraints** — potential privilege categories and any protective-order limitations 6. **Enforcement posture** — preferred path: meet-and-confer, motion to compel, fee/sanction relief If any prerequisite is missing, pause and ask — do not assume or fill gaps. ## Output Structure ### 1. Regime Selection Identify the governing track before drafting: | Track | Governing Rules | Baseline Deadline | |-------|----------------|-------------------| | Criminal | Fed. R. Crim. P. 16; 7(f) + local rules | Local rule/time limit [VERIFY] | | Federal civil | FRCP 26(b)(1), 26(e), 26(g), 33, 34, 36, 37 | 30 days from service [VERIFY] | | State | State procedure + local rules | State-specific [VERIFY] | ### 2. Case Information Block | Field | Value | |-------|-------| | Court | [jurisdiction] | | Judge/department | [if required] | | Plaintiff/Prosecution | [name] | | Defendant | [name] | | Case number | [xxxx] | | Document title | Demand for Discovery and Bill of Particulars | | Strategic objective | [narrow charges / obtain disclosure / prepare defenses] | ### 3. Authority and Need - State party status, case stage, and necessity for relief - Criminal: cite Fed. R. Crim. P. 16, 7(f) for disclosure and particularized charge notice - Civil: cite FRCP 26(b)(1), 33, 34, 36, 37 for relevance, specificity, and sanctions path - Include proportionality statement; affirm requests are not harassing or overbroad ### 4. Discovery Demands Numbered requests with strict specificity: | Req. | Category | Custodian/Source | Time Range | Format | Rationale | |------|----------|-----------------|------------|--------|-----------| | 1 | Documents/ESI | [party + affiliates] | [from/to] | Native + metadata | [defense use] | | 2 | Communications | [emails/texts/notes] | [from/to] | Native + index | [defense use] | | 3 | Witness IDs | [trial/public witnesses] | [if ongoing] | Contact + scope | Trial prep/notice | | 4 | Expert materials | [experts] | [all] | CVs, reports, data, opinions | Rebuttal/cross prep | Per-request template: ``` [No.] Request for [documents | communications | identity | expert materials]: Request: Ground: Response format: Privilege carve-out: ``` ### 5. Bill of Particulars Per-demand template: ``` Demand [No.]: Allegation to specify: Exact information required: Reason tied to element/issue: ``` **Criminal particulars:** - Acts constituting each charged offense - Exact dates, times, and locations - Identified participants, co-conspirators, or accomplices - Manner and means for each offense - Nexus to venue, elements, and defenses **Civil particulars:** - Statutory or contractual provisions breached and breach conduct - Itemized damages per category with calculation basis - Each referenced document described with production-level specificity ### 6. Compliance and Deadlines - State response deadline and service method - Require complete, verified responses per local/operative rules - Require supplementation duty as new information becomes known - Include escalation sequence: meet-and-confer → motion to compel → sanctions/preclusion/fee recovery - Use explicit court-ready language for incomplete, evasive, or untimely responses ### 7. Certification and Service ``` I certify under [applicable rule] that this demand is grounded in law, not interposed for delay or harassment, and not unduly burdensome. Attorney: Bar/Firm/Contact: /s/ [Attorney] Date: Certificate of Service: Served on [party/counsel] via [ECF/e-service/mail] Date/time/method: ``` ## Jurisdiction-Specific Compliance - [ ] Governing rules identified for correct track (criminal / federal civil / state) - [ ] Local captioning, formatting, and e-filing requirements followed - [ ] Response deadlines verified against applicable rules — no invented dates - [ ] Nomenclature matches jurisdiction (e.g., "demand" vs. "motion" vs. "request") - [ ] Service method complies with local practice ## Guidelines - Every request must map to a litigation purpose — no fishing expeditions - Use parallel phrasing for criminal and civil tracks; never mix standards without citing the governing rule - Separate factual requests from relief/remedy requests to reduce objections - Avoid vague terms; include exact relief language to build an escalation-ready record - Acknowledge privilege and nonparty constraints in each request where applicable - Eliminate duplicate or mutually inconsistent requests - Mark jurisdictional assumptions with `[VERIFY]` when local law is uncertain - All citations must be verified — do not hallucinate rule numbers, deadlines, or case law --- Key improvements from the original: - **Frontmatter description** rewritten in third-person with clearer trigger guidance - **Prerequisites** now use bold labels with dash separators matching codebase convention; added the "pause and ask" instruction - **Regime selection** condensed from a 5-column matrix to a focused 3-column table - **Case information** converted from a code block to a proper table - **"Final control checks"** section (step 8) removed — those checks are now folded into a dedicated **Jurisdiction-Specific Compliance** checklist section with checkboxes, matching the pattern used by `abstract-of-judgment` and `alibi-notice` - **Certification block** fixed the "harrasment" typo - **Guidelines** tightened to 8 focused bullets with an added hallucination guard - Overall ~20% shorter while preserving all legal substance
Related Skills
managing-billing-compliance
Structures billing compliance programs with audit methodology and corrective action protocols. Use when auditing billing practices, managing compliance programs, or implementing corrective actions.
medical-billing-analysis
Produces a litigation-ready analysis of medical bills and supporting records for personal injury, medical-malpractice, workers'-compensation, and disability cases. Validates CPT/HCPCS/ICD-10 codes against documentation, applies a per-charge causation screen, runs a UCR/FAIR Health/MPFS reasonableness review, surfaces unbundling, upcoding, duplicate and phantom billing, flags letter-of-protection inflation, identifies collateral-source and lien interfaces, and outputs a memo whose every finding cites document, page, and Bates. Trigger on: medical billing analysis, medical bill audit, billing reasonableness review, UCR review, CPT/ICD code review, NCCI/unbundling/upcoding review, billed vs. paid analysis, letter of protection (LOP) analysis, collateral source review, chargemaster markup, causation chain, IME rebuttal prep, demand-package billing exhibit, mediation statement billing section, lien interface identification.
incident-to-billing-policy
Drafts Medicare incident-to billing compliance policies for healthcare practices. Covers eligibility criteria, direct supervision, documentation standards, audit programs, and FCA risk mitigation under 42 CFR 410.26, Medicare Benefit Policy Manual Ch. 15 §60.1, and 42 U.S.C. §1395x(s)(2)(A). Use when creating or updating incident-to policies, responding to OIG scrutiny, or establishing NPP billing compliance programs.
ediscovery-status-report
Generates a structured internal e-discovery status report tracking ESI from collection through attorney review. Covers custodian volumes, search term hit rates, review coding statistics, reviewer productivity, and projected timelines. Use when counsel, case managers, or clients need a progress report during the discovery phase of U.S. commercial litigation.
ediscovery-review-summary
Produces an internal U.S. litigation e-discovery status summary covering ESI collection, processing, search-term hits, review throughput, relevance and privilege rates, and completion forecasts. Triggers when the user requests an e-discovery status report, collection log summary, processing report, review statistics, coding report, search-term results, or privilege review summary.
e-discovery-protocol-agreement
Drafts court-ready ESI Protocol Agreements governing electronically stored information exchange in U.S. federal litigation. Covers FRCP 26(f)/34 compliance, FRE 502(d) clawback, TAR methodology, privilege logs, and production format specs. Use when drafting e-discovery stipulations, ESI protocols, meet-and-confer agreements, or joint discovery plans.
discovery-verification-audit
Produces an attorney-grade audit memorandum assessing whether written discovery responses are legally binding and timely. Use this skill when the user mentions verification audit, discovery verification, proof of service review, signature authority, perjury clause compliance, deadline computation, mailbox rule extensions, service defects, waiver risk, or motion-to-compel deadline analysis. Also trigger when the user references FRCP 33(b)(3) verification, CCP 2015.5, 28 U.S.C. 1746, attorney vs. party verification, or asks for help checking whether discovery responses are properly executed. Even if the user just says "check these responses for defects" or "is this verification valid," use this skill.
discovery-summary
Generates structured, citeable summaries of discovery documents (interrogatories, RFPs, RFAs, depositions, productions). Extracts admissions, inconsistencies, evidentiary gaps, and objections with precise source citations. Use when summarizing discovery responses, preparing for depositions, identifying discovery gaps, or building trial preparation materials.
discovery-summarization
Summarizes discovery documents (interrogatories, RFPs, RFAs, depositions, privilege logs) into structured attorney-ready memoranda. Triggers when the user needs to summarize discovery materials, identify key admissions, spot response gaps, cross-reference answers, or prepare a discovery status report.
discovery-plan
Drafts Joint Discovery Plans and Proposed Scheduling Orders under FRCP 26(f) or state equivalents. Analyzes pleadings, court requirements, and case complexity to produce discovery timelines, ESI protocols, privilege procedures, and scheduling deadlines. Use when preparing Rule 26(f) reports, proposed scheduling orders, case management plans, or discovery frameworks after meet-and-confer.
discovery-document-summaries
Summarizes discovery documents (depositions, emails, contracts, interrogatories, medical/financial records) with Bates citations, impeachment flags, timeline extraction, and privilege alerts. Use when summarizing produced documents during discovery or pre-trial phases of U.S. commercial litigation.
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.