Back to Details

subpoena-triage

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

/subpoena-triage

/subpoena-triage

  1. Read the subpoena from provided path.
  2. Classify (third-party-docs / third-party-depo / party / CID / grand-jury).
  3. If grand jury → stop, escalate per 
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    . Otherwise continue.
  4. Load 
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml
    for cross-check. Load 
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    → landscape, privilege conventions, escalation norms.
  5. Follow the workflow and reference below.
  6. Extract key fields, analyze scope/burden/privilege, produce objections framework + compliance plan + deadline calendar.
  7. Write 
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/inbound/[slug]/triage.md
    . Copy or link subpoena to 
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/inbound/[slug]/incoming.[ext]
    .
  8. Hand off: 
    /legal-hold --issue
    if hold not in place; 
    /matter-intake
    if materiality warrants; 
    /matter-briefing [slug]
    if party subpoena in existing matter.
  1. 从提供的路径读取传票。
  2. 分类（第三方文件/第三方证词/当事方/CID/大陪审团）。
  3. 若为大陪审团传票→停止操作，按照
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    中的流程升级处理。否则继续下一步。
  4. 加载
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml
    进行交叉核对。加载
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    →了解行业情况、特权惯例、升级规范。
  5. 遵循以下工作流程并参考相关内容。
  6. 提取关键字段，分析范围/负担/特权，生成异议框架+合规计划+截止日历。
  7. 写入
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/inbound/[slug]/triage.md
    。将传票复制或链接至
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/inbound/[slug]/incoming.[ext]
    。
  8. 移交：若未实施法律保留，执行
    /legal-hold --issue
    ；若重要性符合要求，执行
    /matter-intake
    ；若为现有案件中的当事方传票，执行
    /matter-briefing [slug]
    。

Subpoena Triage

传票分类处理

Purpose

目的

Subpoenas arrive with deadlines. The failure modes: missing the deadline, over-producing (privilege waiver, burden we should have objected to), under-producing (contempt exposure), or missing a motion-to-quash window. This skill classifies, analyzes, and produces a compliance plan with objections framework.
传票附带截止期限，常见失误包括：错过截止日期、过度提供文件（导致特权放弃、本应提出异议的负担）、提供不足（面临藐视法庭风险），或错过撤销动议的窗口期。本技能可对传票进行分类、分析，并生成带有异议框架的合规计划。

Jurisdiction assumption

管辖权假设

The rule cited in Step 0 is the operative one for this subpoena in this forum. Subpoena practice varies materially: federal (FRCP 45) vs. state equivalents, state-to-state variants, local rules, court-specific standing orders, and the subpoena type (trial, deposition, document production) all change objection deadlines, place-of-compliance limits, privilege-log requirements, and cost-shifting. Every rule output here is a starting-point heuristic — confirm currency and the local variant before asserting in writing.
步骤0中引用的规则是本次传票在对应法庭的适用规则。传票操作流程差异显著：联邦规则（FRCP 45）与各州等效规则、州与州之间的变体、当地规则、法院特定常规命令，以及传票类型（审判、证词、文件提供）都会改变异议截止日期、合规地点限制、特权日志要求和成本转移规则。此处输出的所有规则均为初始启发式内容——在书面主张前，请确认规则的时效性和当地变体。

Side context

立场背景

This skill is inherently defensive — a subpoena has been served on the recipient and the posture is respond/object/comply. Read 
## Side
in the practice profile. If the user's default side is plaintiff, note that receiving a subpoena is common for plaintiffs too (witness subpoenas, third-party requests directed at the plaintiff's own records) but the framing here is always "subpoena served on us, how do we respond." If the user is defense (typical), the framing aligns with the default. If the matter has a different posture than the default (e.g., defense practitioner receiving a subpoena in a matter where they're pro se for a family member), prompt the user to confirm posture before proceeding.
本技能本质上属于防御性工具——传票已送达接收方，需采取回应/异议/合规的应对姿态。请阅读实践档案中的
## Side
部分。若用户默认立场为原告，需注意原告收到传票也很常见（证人传票、针对原告自身记录的第三方请求），但本技能始终以“传票送达我方，应如何回应”为框架。若用户为被告（典型情况），则框架与默认设定一致。若案件立场与默认不同（例如，被告律师在为家人代理的自诉案件中收到传票），请提示用户确认立场后再继续。

Load context

加载上下文

  • The subpoena document (user provides path or drops it in-session)
  • ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml
    — for related matter lookup and legal hold status
  • ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    → landscape (regulators we deal with), house privilege conventions, escalation norms
  • 传票文件（用户提供路径或在会话中上传）
  • ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml
    — 用于相关案件查询和法律保留状态确认
  • ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    → 行业情况（我们对接的监管机构）、内部特权惯例、升级规范

Workflow

工作流程

Step 0: Research the applicable rule

步骤0：研究适用规则

Before analyzing this subpoena, research the applicable rule of civil procedure for the forum (FRCP 45 for federal, the state equivalent otherwise) and the subpoena type (trial, deposition, document production). Identify: place-of-compliance limits, objection deadlines (these often run from the EARLIER of the compliance date or a fixed number of days after service), privilege-log requirements, and who bears costs. Cite with pinpoint references. Verify currency — rules and local variants change. Flag grand-jury subpoenas for immediate criminal-counsel escalation.
No silent supplement. If a research query to the configured legal research tool (Westlaw, CourtListener, Trellis, Descrybe, or firm platform) returns few or no results for the forum's rule, variant, or pinpoint, 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 / forum / variant]. 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) 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, case, statute, and regulation in the triage output with where it came from: 
[Westlaw]
, 
[CourtListener]
, 
[Trellis]
, 
[Descrybe]
, or the MCP tool name for citations retrieved from a legal research connector; 
[web search — verify]
for citations from web search; 
[model knowledge — verify]
for citations recalled from training data; 
[user provided]
for citations the user supplied (e.g., from the subpoena or prior matter work). Citations tagged 
verify
carry higher fabrication risk and should be checked first. Never strip or collapse the tags — they are counsel's fastest signal about which citations to verify before asserting in objections or filings.
在分析本次传票前，研究对应法庭的适用民事诉讼规则（联邦案件为FRCP 45，州案件为各州等效规则）以及传票类型（审判、证词、文件提供）。明确：合规地点限制、异议截止日期（通常为合规日期或送达后固定天数中的较早者）、特权日志要求，以及成本承担方。请精准引用规则。确认时效性——规则和当地变体可能发生变化。标记大陪审团传票，需立即升级至刑事律师处理。
**禁止补充未核实内容。**若向配置的法律研究工具（Westlaw、CourtListener、Trellis、Descrybe或律所平台）发起的研究查询，对法庭规则、变体或精准引用的结果较少或无结果，请报告已发现内容并停止操作。请勿未经询问就通过网络搜索或模型知识填补空白。应告知用户：“从[工具]中搜索到[N]条结果。[规则/法庭/变体]的覆盖范围较窄。可选方案：(1) 扩大搜索查询范围，(2) 尝试其他研究工具，(3) 进行网络搜索——结果将标记为
[web search — verify]
，在依赖前需对照原始来源核实，或(4) 在此停止。您希望选择哪种方案？”律师有权决定是否接受低可信度来源；本技能不得自行决定。
**来源归因。**在分类处理输出中，为每个规则引用、案例、法规和条例标记来源：从法律研究连接器获取的引用标记为
[Westlaw]
、
[CourtListener]
、
[Trellis]
、
[Descrybe]
或MCP工具名称；网络搜索获取的引用标记为
[web search — verify]
；训练数据中召回的引用标记为
[model knowledge — verify]
；用户提供的引用（例如来自传票或先前案件工作）标记为
[user provided]
。标记
verify
的引用存在更高的伪造风险，应优先核实。切勿移除或合并这些标记——它们是律师快速判断哪些引用需在异议或文件中主张前核实的关键信号。

Step 1: Classify

步骤1：分类

Subpoenas come in flavors with different rules; confirm the specifics against the rule you just researched:
  • Third-party document subpoena (civil) — we're not a party to the litigation; someone wants our documents. Usual objection categories: relevance, burden, privilege, place-of-compliance / geographic reach.
  • Third-party deposition subpoena — someone wants an employee to testify. Scope, relevance, burden; possible motion to quash; witness prep required.
  • Party subpoena — we ARE a party; this is discovery in a litigation we're tracking. Treat as discovery, not inbound — it should map to an existing matter.
  • Regulatory civil investigative demand (CID) — FTC, SEC, DOJ, state AG. Different rules, different posture; often more deferential but also more consequential.
  • Grand jury subpoena — criminal. Escalate immediately to criminal counsel; different skill path (outside this skill's scope — flag for escalation).
传票有多种类型，对应不同规则；请对照刚研究的规则确认具体类型：
  • 第三方文件传票（民事）——我方并非诉讼当事方；他人要求我方提供文件。常见异议类别：相关性、负担、特权、合规地点/地理范围。
  • 第三方证词传票——他人要求我方员工作证。需考量范围、相关性、负担；可能需提出撤销动议；需为证人做准备。
  • 当事方传票——我方为诉讼当事方；这是我方跟踪的诉讼中的证据开示环节。将其视为证据开示，而非外来请求——应关联至现有案件。
  • 监管民事调查令（CID）——来自FTC、SEC、DOJ、州总检察长。规则和立场不同；通常更需顺从，但后果也更严重。
  • 大陪审团传票——刑事案件。立即升级至刑事律师处理；本技能不涵盖此类传票的处理路径——标记为需升级。

Step 2: Extract key fields

步骤2：提取关键字段

  • Issuing authority — court (which), agency (which), counsel (if civil)
  • Issuing party — who requested (if civil)
  • Case / matter caption — the litigation we're being asked about
  • Document categories sought — numbered list
  • Testimony topics (if depo) — Rule 30(b)(6) designations
  • Deadline for response/objection — date served + computing the response window per applicable rule
  • Production date — date by which documents must be produced
  • Geographic scope — custodians, locations, systems implicated
  • Custodian of record designation — who at the company is the witness/signatory
  • 签发机构——法院（具体哪一家）、机构（具体哪一家）、律师（民事案件）
  • 签发方——提出请求的主体（民事案件）
  • 案件标题——涉及的诉讼案件
  • 要求提供的文件类别——编号列表
  • 证词主题（若为证词传票）——Rule 30(b)(6)指定内容
  • 回应/异议截止日期——送达日期+根据适用规则计算的回应窗口期
  • 文件提供日期——需完成文件提供的日期
  • 地理范围——涉及的保管人、地点、系统
  • 记录保管人指定——公司中担任证人/签署人的人员

Step 3: Portfolio cross-check

步骤3：案件组合交叉核对

  • Party subpoena → related to existing matter: verify the caption matches a matter in 
    _log.yaml
    . If yes, route to that matter's workflow; this triage is informational.
  • Third-party subpoena → caption we don't recognize: capture the parties; log as standalone inbound.
  • Multiple subpoenas from same case: flag coordinated issuance; a single response strategy may apply.
  • **当事方传票→关联至现有案件：**确认案件标题与
    _log.yaml
    中的案件匹配。若匹配，路由至该案件的工作流程；本次分类处理仅作参考。
  • **第三方传票→标题未识别：**记录当事方；作为独立外来请求记录。
  • **同一案件的多份传票：**标记为协同签发；可采用统一回应策略。

Step 4: Analyze scope, burden, privilege

步骤4：分析范围、负担、特权

Scope / relevance
  • Do the categories map to actual documents we plausibly have?
  • Is any category a fishing expedition (overbroad, untethered to claims/defenses of the underlying case)?
  • Place of compliance / geographic reach — apply the researched rule; limits differ by subpoena type (trial vs. document vs. deposition).
Burden
  • Custodians implicated, systems searched, time period
  • Estimated volume (rough: small / medium / large / extreme)
  • Cost — third-party responders may have cost-shifting available; check the researched rule.
Privilege
  • Attorney-client or work product likely implicated? (Almost always yes for anything legal-related; often yes for communications involving in-house or outside counsel.)
  • Other privileges — trade secret, HIPAA (if applicable), state privilege, common interest
  • Privilege log will be required — flag the format per 
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
Other objection grounds
  • Confidentiality — protective order needed?
  • Duplicative — do they already have this from another party?
  • Not possessed — we don't have what they're asking for (document with specificity)
  • Improperly served — check the researched rule's service requirements
范围/相关性
  • 要求的类别是否与我方实际可能拥有的文件匹配？
  • 是否存在钓鱼式请求（范围过宽、与基础案件的主张/抗辩无关）？
  • 合规地点/地理范围——应用研究的规则；不同传票类型（审判/文件/证词）的限制不同。
负担
  • 涉及的保管人、需搜索的系统、时间范围
  • 预估文件量（大致：小/中/大/极大）
  • 成本——第三方响应方可能可申请成本转移；请查阅研究的规则。
特权
  • 是否可能涉及律师-客户特权或工作成果特权？（几乎所有法律相关内容都会涉及；涉及内部或外部律师的沟通通常也会涉及。）
  • 其他特权——商业秘密、HIPAA（如适用）、州特权、共同利益
  • 需提供特权日志——根据
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    标记格式要求
其他异议理由
  • 保密性——是否需要保护令？
  • 重复性——对方是否已从其他当事方获取相关内容？
  • 未持有——我方不拥有对方要求的内容（需具体说明文件）
  • 送达不当——检查研究的规则中的送达要求

Step 5: Objections framework

步骤5：异议框架

Draft a structured objections outline — not the final objections letter, but the outline of what objections apply and why. The user (often with outside counsel) finalizes.
Each objection:
  • Legal basis — cite the pinpoint from the rule researched in Step 0
  • Specific application to this subpoena (which categories, which custodians)
  • Strength (strong / reasonable / weak)
起草结构化的异议大纲——并非最终异议函，而是列出适用的异议及理由的大纲。用户（通常会同外部律师）将完成最终版本。
每个异议需包含：
  • 法律依据——引用步骤0中研究的规则精准内容
  • 针对本次传票的具体应用（涉及哪些类别、哪些保管人）
  • 强度（强/合理/弱）

Step 6: Compliance plan

步骤6：合规计划

Even when objecting, we often produce some of what's requested. Plan:
  • Scope of likely production — after objections, what we'd produce
  • Custodians to search — names and systems
  • Date range
  • Review protocol — who reviews for privilege (us, outside counsel, contract reviewers)
  • Production format — per the subpoena or per negotiated protocol (TIFF+load file, native, PDF)
  • Privilege log requirements — format, fields
即使提出异议，我方通常仍需提供部分请求内容。计划内容：
  • 可能提供的范围——提出异议后，我方将提供的内容
  • 需搜索的保管人——姓名和系统
  • 日期范围
  • 审核流程——谁负责特权审核（我方、外部律师、合同审核员）
  • 提供格式——按照传票要求或协商后的流程（TIFF+加载文件、原生格式、PDF）
  • 特权日志要求——格式、字段

Step 7: Deadlines

步骤7：截止日期

Use the deadlines identified in the Step 0 research. Note that objection deadlines often run from the EARLIER of the compliance date or a fixed number of days after service — do not default to a single number without checking the applicable rule and local variant.
  • Response deadline — per researched rule; note if user needs more time (meet-and-confer to extend is standard)
  • Objection deadline — per researched rule (federal / state rule + any local variant)
  • Production date — if no objections succeed
  • Motion to quash window — if pursuing that path, timing is critical
Calendar all of them. Immediate action item.
使用步骤0研究中确定的截止日期。注意异议截止日期通常为合规日期或送达后固定天数中的较早者——请勿在未检查适用规则和当地变体的情况下默认采用单一天数。
  • 回应截止日期——根据研究的规则；若用户需要更多时间，标准做法是协商延期
  • 异议截止日期——根据研究的规则（联邦/州规则+任何当地变体）
  • 文件提供日期——若异议均未获支持
  • 撤销动议窗口期——若选择此路径，时间至关重要
将所有日期纳入日历。这是立即执行的行动项。

Step 8: Write triage

步骤8：撰写分类处理报告

Output: 
~/.claude/plugins/config/claude-for-legal/litigation-legal/inbound/[slug]/triage.md
.
markdown
[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]
输出至：
~/.claude/plugins/config/claude-for-legal/litigation-legal/inbound/[slug]/triage.md
。
markdown
[工作成果标题 — 根据插件配置## Outputs — 因角色而异；请参阅`## Who's using this`]

Subpoena Triage

Subpoena Triage

NOT A SUBSTITUTE FOR OUTSIDE COUNSEL. This is a structured classification and scoping read to support fast decisions on deadlines, holds, and engagement. Every rule reference is a starting-point heuristic; jurisdiction-specific analysis, objections finalization, motions practice, and merit calls on privilege require licensed counsel familiar with the forum. Engage outside counsel for any subpoena above routine third-party document scope.
Slug: [slug] Served: [YYYY-MM-DD] Served on: [entity / registered agent] Incoming file: [path] Classification: [third-party-docs / third-party-depo / party / CID / grand-jury]
**不能替代外部律师。**这是结构化的分类和范围界定分析，用于支持关于截止日期、保留措施和协作的快速决策。所有规则引用均为初始启发式内容；管辖权特定分析、异议定稿、动议操作以及特权的实质性判断，需由熟悉对应法庭的持证律师完成。对于超出常规第三方文件范围的任何传票，请聘请外部律师。
Slug: [slug] Served: [YYYY-MM-DD] Served on: [entity / registered agent] Incoming file: [path] Classification: [third-party-docs / third-party-depo / party / CID / grand-jury]

Key fields

Key fields

  • Issuing authority: [court/agency]
  • Issuing party: [name]
  • Case caption: [caption]
  • Response deadline: [date]
  • Production date: [date]
  • Motion-to-quash window: [date range]
  • Issuing authority: [court/agency]
  • Issuing party: [name]
  • Case caption: [caption]
  • Response deadline: [date]
  • Production date: [date]
  • Motion-to-quash window: [date range]

Categories sought (summary)

Categories sought (summary)

[numbered list, concise]
[numbered list, concise]

Custodians / systems likely implicated

Custodians / systems likely implicated

[list]
[list]

Portfolio cross-check

Portfolio cross-check

Related matter: [slug or "none"] If party subpoena: [routed to existing matter or new matter?] If third-party: [standalone inbound]
Related matter: [slug or "none"] If party subpoena: [routed to existing matter or new matter?] If third-party: [standalone inbound]

Scope & burden analysis

Scope & burden analysis

Scope: [relevance assessment by category] Burden estimate: [small / medium / large / extreme — with reasoning] Geographic reach issues: [any]
Scope: [relevance assessment by category] Burden estimate: [small / medium / large / extreme — with reasoning] Geographic reach issues: [any]

Privilege analysis

Privilege analysis

Privilege scoping is a first-pass read; final call is counsel's, not this skill's.
Attorney-client / work product likely implicated: [yes/no + which categories] 
[SME VERIFY]
Other privileges: [trade secret, HIPAA, state, common interest] 
[SME VERIFY]
Privilege log format required: [per 
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
]
Privilege scoping is a first-pass read; final call is counsel's, not this skill's.
Attorney-client / work product likely implicated: [yes/no + which categories] 
[SME VERIFY]
Other privileges: [trade secret, HIPAA, state, common interest] 
[SME VERIFY]
Privilege log format required: [per 
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
]

Objections framework

Objections framework

Every row below requires 
[SME VERIFY]
before asserting in writing — jurisdiction, rule currency, waiver risk.
ObjectionLegal basisApplies toStrengthSME verified?
Relevance[rule][categories][strong/reasonable/weak][ ]
Burden[rule][categories][ ]
PrivilegeA/C, WP[all producing docs]strong (always)[ ]
Duplicative[rule/doctrine][if applicable][ ]
[other][ ]
Every row below requires 
[SME VERIFY]
before asserting in writing — jurisdiction, rule currency, waiver risk.
ObjectionLegal basisApplies toStrengthSME verified?
Relevance[rule][categories][strong/reasonable/weak][ ]
Burden[rule][categories][ ]
PrivilegeA/C, WP[all producing docs]strong (always)[ ]
Duplicative[rule/doctrine][if applicable][ ]
[other][ ]

Compliance plan (if responding)

Compliance plan (if responding)

  • Scope of likely production: [after objections]
  • Custodians / systems: [list]
  • Date range: [range]
  • Review protocol: [who, how]
  • Production format: [format]
  • Privilege log: [format, est. entries]
  • Scope of likely production: [after objections]
  • Custodians / systems: [list]
  • Date range: [range]
  • Review protocol: [who, how]
  • Production format: [format]
  • Privilege log: [format, est. entries]

Deadlines (calendar these)

Deadlines (calendar these)

All deadlines below come from the Step 0 rule research. 
[SME VERIFY]
confirms the rule, variant, and computation for this forum and this subpoena type — state variants and local rules differ.
  • Response deadline: [date] 
    [SME VERIFY]
  • Objection deadline: [date] — cite: [rule + pinpoint] 
    [SME VERIFY]
  • Meet-and-confer by: [date] (typically before objection deadline) 
    [SME VERIFY]
  • Production date: [date]
All deadlines below come from the Step 0 rule research. 
[SME VERIFY]
confirms the rule, variant, and computation for this forum and this subpoena type — state variants and local rules differ.
  • Response deadline: [date] 
    [SME VERIFY]
  • Objection deadline: [date] — cite: [rule + pinpoint] 
    [SME VERIFY]
  • Meet-and-confer by: [date] (typically before objection deadline) 
    [SME VERIFY]
  • Production date: [date]

Immediate actions

Immediate actions

  • Legal hold issued — [yes/no] — if no, run 
    /legal-hold [slug] --issue
    with subpoena scope
  • Outside counsel engaged — [yes/who/TBD]
  • Meet-and-confer scheduled — [date]
  • Matter created in log — [yes/no/TBD — usually yes for anything above the smallest third-party docs subpoena]
  • Insurance / cost-shifting analysis — [if burden is large]
  • Internal escalation — [who]
  • Legal hold issued — [yes/no] — if no, run 
    /legal-hold [slug] --issue
    with subpoena scope
  • Outside counsel engaged — [yes/who/TBD]
  • Meet-and-confer scheduled — [date]
  • Matter created in log — [yes/no/TBD — usually yes for anything above the smallest third-party docs subpoena]
  • Insurance / cost-shifting analysis — [if burden is large]
  • Internal escalation — [who]

Recommendation

Recommendation

[Two paragraphs: what to do. Objection posture. Production posture. Whether outside counsel handles objections or we do. Whether to move to quash.]
[Two paragraphs: what to do. Objection posture. Production posture. Whether outside counsel handles objections or we do. Whether to move to quash.]

Citation verification

Citation verification

Every rule reference, case, statute, and regulation in this triage — including the Step 0 research citations, objection bases, and the privilege-log format pointer — is AI-generated and unverified. Before relying on any cite (especially in objections, a motion to quash, or correspondence with the issuing party), run a verification pass against a legal research tool (Westlaw, CourtListener, Trellis, Descrybe, or your firm's platform) for accuracy, good law status, and local variants. Fabricated or misquoted citations in filed documents have resulted in sanctions. Source tags on each citation (e.g., 
[Westlaw]
, 
[web search — verify]
) show where it came from; 
verify
tags carry higher fabrication risk and should be checked first.
undefined
Every rule reference, case, statute, and regulation in this triage — including the Step 0 research citations, objection bases, and the privilege-log format pointer — is AI-generated and unverified. Before relying on any cite (especially in objections, a motion to quash, or correspondence with the issuing party), run a verification pass against a legal research tool (Westlaw, CourtListener, Trellis, Descrybe, or your firm's platform) for accuracy, good law status, and local variants. Fabricated or misquoted citations in filed documents have resulted in sanctions. Source tags on each citation (e.g., 
[Westlaw]
, 
[web search — verify]
) show where it came from; 
verify
tags carry higher fabrication risk and should be checked first.
undefined

Step 9: Hand off

步骤9：移交

Before responding to the subpoena (serving objections, producing documents, appearing for deposition, or filing a motion to quash — any substantive response to the issuing party or court): Read 
## Who's using this
in 
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
. If the Role is Non-lawyer:
Responding to a subpoena has legal consequences — missing a deadline risks contempt, over-producing waives privilege, under-producing risks sanctions. 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 subpoena type, issuing authority, deadlines, scope of what's sought, objections framework and strength, privilege and burden issues, proposed response posture, what could go wrong, 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 proceed past this gate without an explicit yes. Triage, scoping, and internal calendaring do not require the gate — the response to the issuing authority does.
  • If classified as grand jury subpoena → stop, flag for escalation per 
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    , do not proceed with standard triage.
  • If classified as CID: flag that regulator-specific norms apply; recommend outside regulatory counsel.
  • Otherwise: offer to create a matter (usually yes — subpoenas are almost always material enough to track).
  • If a legal hold isn't issued with subpoena scope, hand off to 
    /legal-hold --issue
    immediately.
**在回应传票前（送达异议、提供文件、出庭作证或提交撤销动议——任何向签发方或法庭作出的实质性回应）：**请阅读
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
中的
## Who's using this
部分。若角色为非律师：
回应传票会产生法律后果——错过截止日期可能面临藐视法庭指控，过度提供文件会放弃特权，提供不足可能面临处罚。您是否已与律师审核过此内容？若是，请继续。若否，以下是一份可提交给律师的摘要：
[生成1页摘要：传票类型、签发机构、截止日期、要求内容范围、异议框架及强度、特权和负担问题、建议的回应姿态、可能出现的问题、需向律师询问的事项。]
若您需要在所在司法管辖区寻找持证律师、事务律师、出庭律师或其他授权法律专业人士：您所在行业的监管机构推荐服务是最快的起点（美国为州律师协会，英格兰和威尔士为SRA/律师标准委员会，苏格兰/北爱尔兰/爱尔兰/加拿大/澳大利亚为律师协会，或您所在司法管辖区的等效机构）。
未获得明确同意前，请勿越过此环节。分类处理、范围界定和内部日程安排无需此环节——但向签发方作出回应需要。
  • 若分类为大陪审团传票→停止操作，按照
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    中的流程标记为需升级，请勿继续标准分类处理。
  • 若分类为CID：标记需适用监管机构特定规范；建议聘请外部监管律师。
  • 其他情况：提议创建案件（通常为是——传票几乎都具备足够重要性，需进行跟踪）。
  • 若未针对传票范围实施法律保留，立即移交至
    /legal-hold --issue
    处理。

Close with the next-steps decision tree

以下一步决策树收尾

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.
根据CLAUDE.md中的
## Outputs
，以下一步决策树收尾。根据本技能生成的内容自定义选项——五个默认分支（起草X、升级、获取更多事实、观望等待、其他）为起点，并非固定选项。决策树为输出内容，由律师选择。

What this skill does not do

本技能不涵盖的内容

  • Draft the final objections letter. Produces the framework; the letter is drafted by user + outside counsel (future: a dedicated objections-draft skill).
  • Move to quash. Surfaces the option; the motion is legal work that requires jurisdiction-specific analysis.
  • Validate rules across jurisdictions. The Step 0 research produces the operative rule for this subpoena; the skill doesn't independently confirm currency or local variants. Flag for counsel verification before acting.
  • Handle grand jury subpoenas. Escalates. This is outside the triage scope.
  • **起草最终异议函。**仅生成框架；异议函由用户+外部律师起草（未来将推出专门的异议起草技能）。
  • **提交撤销动议。**仅提出该选项；动议属于法律工作，需进行管辖权特定分析。
  • **跨管辖权验证规则。**步骤0的研究生成本次传票的适用规则；本技能不会独立确认规则的时效性或当地变体。在采取行动前，标记需律师验证。
  • **处理大陪审团传票。**仅升级处理。此类传票不在分类处理范围内。