Help us improve
Share bugs, ideas, or general feedback.
From litigation-legal
First-pass privilege log review: flags obviously privileged and obviously non-privileged entries, identifies entries needing attorney review. Use when reviewing a privilege log before production.
npx claudepluginhub anthropics/claude-for-legal --plugin litigation-legalHow this skill is triggered — by the user, by Claude, or both
Slash command
/litigation-legal:privilege-log-review [log file, or document set][log file, or document set]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. Load `~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md` → review protocol, priv log format.
Reviews documents for attorney-client privilege (Av.K. m.36) and trade secrets before submission to court, prosecutor, or competition authority. Flags clearly privileged/non-privileged items and marks ambiguous ones for attorney review.
Manages internal investigations from intake through final memo: privileged log, document processing, source coverage tracking, Q&A, memo drafting, and audience summaries.
Triage inbound NDAs into GREEN / YELLOW / RED so legal only reviews the ones that need it. Applies a configurable playbook for sales-side or purchasing-side review.
Share bugs, ideas, or general feedback.
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md → review protocol, priv log format.Before working with a set of litigation documents, ask: "Were any of these documents obtained through disclosure or discovery in legal proceedings?" If yes:
Confirm: "This use is within the proceedings in which the documents were disclosed, or I have permission / consent, or the documents are now public." If not confirmed, flag it: "⚠️ Disclosed documents may have use restrictions. Confirm this use is permitted before proceeding."
Matter context. Check ## Matter workspaces in the practice-level CLAUDE.md. For litigation-legal the default is Enabled: ✓ — every case gets its own matter workspace. If Enabled is ✗ (you turned it off because you work one case at a time), skip the rest of this paragraph and use practice-level context. If enabled and there is no active matter, ask: "Which matter is this for? Run /litigation-legal:matter-workspace switch <slug> or say practice-level." Load the active matter's matter.md for matter-specific context and overrides. Write outputs to the matter folder at ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.
A privilege log has three kinds of entries: obviously privileged, obviously not, and the ones that need thought. This skill sorts the first two kinds so the attorney's time goes entirely to the third.
This is first pass. Attorney reviews every flag. No exceptions.
When this skill cites a rule, local variant, or authority for a privilege call (FRCP 26(b)(5)(A), state rule, local rule, case on waiver scope, case on dominant purpose), two rules apply.
Pinpoint cites must support the whole proposition. If the review cites one rule or case to support a multi-part proposition — "the log must describe each document and withhold only materials prepared in anticipation of litigation" — verify the pinpoint covers every element. If it only covers one, split the cite or narrow the proposition. A cite that backs part of a privilege position gets the position rejected when opposing counsel reads the cite and points out it doesn't reach the contested element. This is the "misgrounded citation" failure mode: the cite exists, the passage exists, but it doesn't support the proposition as stated.
Extract all citations before checking any. When this review cites authority — or when a separate citation-check is requested on the log, a related brief, or the supporting motion:
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md → privilege log format, review protocol.
Conflicts gate — unbypassable. Before reviewing a privilege log, check ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml for the matter slug. If the matter is not in _log.yaml, refuse and route:
"I don't see [matter slug] in the matter log. Run
/litigation-legal:matter-intakefirst so the conflicts check runs and the matter workspace is set up. I won't review a privilege log on a matter that hasn't been intaken — the conflicts check is the gate, and a privilege log review is work product that needs to live in the matter file."
Jurisdiction matters. Privilege scope (A/C and work product), waiver doctrine, and log-form requirements vary materially across federal circuits and state courts. This review applies the rules for the forum specified in config. If the matter involves a different forum, a transferred case, multi-jurisdictional production, or a choice-of-law question on privilege, the calls here may not transfer — re-run against the controlling forum.
Before reviewing entries, research the forum's privilege-log requirements (FRCP 26(b)(5)(A) or state equivalent), any local rule variant, and the judge's standing orders. Identify the required fields, the level of description, and any category-log or metadata-log accommodations. Cite primary sources.
No silent supplement. If a research query to the configured legal research tool (Lexis+, Westlaw, CourtListener, Trellis, Descrybe, or firm platform) returns few or no results for the forum's rule, waiver doctrine, or local variant, report what was found and stop. Do NOT fill the gap from web search or model knowledge without asking. Say: "The search returned [N] results from [tool]. Coverage appears thin for [rule / doctrine]. Options: (1) broaden the search query, (2) try a different research tool, (3) search the web — results will be tagged [web search — verify] and should be checked against a primary source before relying, or (4) leave the [UNCERTAIN] marker and stop here. Which would you like?" A lawyer decides whether to accept lower-confidence sources; the skill does not decide for them.
Source attribution. Tag every rule reference and authority in the review output with where it came from: [Lexis+], [Westlaw], [CourtListener], [Trellis], [Descrybe], or the MCP tool name for citations retrieved from a legal research connector; [web search — verify] for web-search citations; [model knowledge — verify] for citations recalled from training data; [user provided] for citations the reviewing attorney supplied. Citations tagged verify carry higher fabrication risk and should be checked first. Never strip or collapse the tags — they are the reviewing attorney's signal about which authorities to re-confirm before service.
Waiver doctrine differs by privilege type:
Confirm the forum's waiver doctrine for each privilege claimed before recommending production of anything. [UNCERTAIN] flags stay on waiver calls until counsel confirms.
Three-state rule. The skill never silently decides a subjective threshold isn't met. On any uncertain call — dominant purpose unclear, litigation contemplation borderline, mixed legal/business content, ambiguous third-party presence — the skill keeps the privilege designation on and adds a ⚠️ flag for the attorney. Under-marking waives privilege (one-way door); over-marking is corrected by the attorney in review (two-way door). Prefer the recoverable error.
In-house counsel privilege is jurisdiction-specific and contested. Before classifying any communication with in-house counsel as privileged, check the jurisdiction:
Never classify an in-house counsel communication as "confidently privileged" without stating which privilege regime applies. If the matter involves non-US jurisdictions, especially EU competition or any EU regulator: "Documents from in-house counsel may have NO privilege in [jurisdiction]. Under Akzo Nobel, in-house communications are compellable in EU competition proceedings. Flag for review by a [jurisdiction] litigation specialist before asserting privilege."
The ✅ "confidently privileged, no flag" tier below is the one designed to bypass attorney review. That's exactly where the Akzo Nobel risk lives. When the jurisdiction is non-US or the matter touches EU regulators, there is no ✅ tier for in-house communications — everything goes to 🟡 "flag for attorney review with jurisdiction note."
The default for anything that isn't confidently in ✅ or ❌. The skill does not withhold a privilege designation on its own assessment of a subjective test. Examples:
Each flag records the specific open question and the evidence cutting each way, so the attorney can decide without re-reading the document cold.
Only for the unambiguous cases. The output still records the assessment rationale so the attorney can spot-check; it does not remove the designation from the log on its own.
If any of these is close — the third party might be an agent, the lawyer's CC might actually be on a legal request — it's uncertain, not ❌. Route it to the uncertain bucket and flag.
Does the log have what it needs?
| Field | Present? |
|---|---|
| Date | |
| Author | |
| Recipients (all — TO, CC, BCC) | |
| Document type | |
| Privilege claimed (A/C, WP, both) | |
| Description (enough to assess without revealing privileged content) |
Missing fields → flag for completion before substantive review.
For each entry:
Entry [N] ([Bates]): [✅ Priv | ✅ Priv + ⚠️ Flag | ❌ Not priv (assessed)]
[If ✅ (no flag): one-line reason]
[If ✅ + ⚠️: keep designation; the specific question the attorney needs to answer; evidence cutting each way]
[If ❌: one-line reason — but the designation stays on the log until the attorney removes it]
Never produce an entry that silently strips a privilege designation based on the skill's own subjective call. A ❌ is a recommendation logged alongside the flag; the attorney acts on it.
Across the log:
Before the privilege log is served on the opposing party (the consequential act — this includes serving the log AND designating documents withheld or produced under a protective-order designation such as Confidential / Highly Confidential / AEO): Read ## Who's using this in ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md. If the Role is Non-lawyer:
Submitting a privilege log and designating documents in discovery both have legal consequences — over-designation risks sanctions and loss of credibility; under-designation risks waiver; a misdesignated production may be unrecallable. Have you reviewed this with an attorney? If yes, proceed. If no, here's a brief to bring to them:
[Generate a 1-page summary: the matter, log entry counts, the ⚠️ flags and close calls, pattern observations (over-designation, vague descriptions), waiver-doctrine posture by privilege type, what could go wrong on service or designation, what to ask the attorney.]
If you need to find a licensed attorney, solicitor, barrister, or other authorised legal professional in your jurisdiction: your professional regulator's referral service is the fastest starting point (state bar in the US, SRA/Bar Standards Board in England & Wales, Law Society in Scotland/NI/Ireland/Canada/Australia, or your jurisdiction's equivalent).
Do not treat the log as service-ready without an explicit yes. First-pass review, sorting, and flagging do not require the gate — service and designation do.
[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]
## Privilege Log Review: [Matter] — [date]
**Applicable rule:** [FRCP 26(b)(5)(A) / state rule / local rule / standing order — pinpoint cites] `[UNCERTAIN — verify currency]`
**Entries reviewed:** [N]
**Results:** [N] ✅ confident priv / [N] ✅+⚠️ priv kept & flagged / [N] ❌ recommend remove (attorney confirms)
### ✅ + ⚠️ Flagged — designation kept, attorney decides
| Entry | Bates | Issue | Evidence for priv | Evidence against | Question |
|---|---|---|---|---|---|
| [N] | [range] | [what's subjective] | [one line] | [one line] | [the specific call to make] |
### ❌ Recommend remove designation (attorney confirms before stripping)
| Entry | Bates | Reason |
|---|---|---|
*Recorded, not executed. The skill does not remove privilege designations from the log — the attorney does, after reviewing the rationale.*
### ✅ Privileged (no action)
[Count. List available on request.]
### Pattern observations
[Repeating issues, over-designation, description problems]
### Marker discipline
- `[VERIFY: factual assertion about document/custodian/date]`
- `[UNCERTAIN: close privilege call / waiver scope / doctrine question]`
- `[CITE NEEDED: rule, local variant, or authority supporting a call]`
---
**Attorney must review all ⚠️ and ❌ before any action.**
**Privileged source material.** This review reads entries and underlying documents that are, by definition, privilege-candidate material. The review output inherits that status — keep it with privileged materials, mark it appropriately, and don't circulate outside the privilege circle. Distributing it can itself waive protection.
End with the next-steps decision tree per CLAUDE.md ## Outputs. Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.