Back to Details

ai-tool-handoff

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

AI Tool Handoff

AI工具交接

Matter context

事项上下文

Matter context. Check 
## Matter workspaces
in the practice-level CLAUDE.md. If 
Enabled
is 
✗
(the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run 
/corporate-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/corporate-legal/matters/<matter-slug>/
. Never read another matter's files unless 
Cross-matter context
is 
on
.
事项上下文。查看业务级CLAUDE.md中的
## Matter workspaces
部分。如果“Enabled”为
✗
（内部用户默认设置），则跳过本段剩余内容——技能将使用业务级上下文，事项机制不可见。如果已启用且无活跃事项，请询问：“这是针对哪个事项的？运行
/corporate-legal:matter-workspace switch <slug>
或说明‘业务级’。”加载活跃事项的
matter.md
以获取事项特定上下文和覆盖配置。将输出写入事项文件夹：
~/.claude/plugins/config/claude-for-legal/corporate-legal/matters/<matter-slug>/
。除非“Cross-matter context”设置为“on”，否则切勿读取其他事项的文件。

Purpose

目的

Luminance and Kira are good at one thing: reading 500 contracts and finding every change-of-control clause. They're less good at judgment — deciding whether a particular CoC provision is actually triggered by this deal structure.
This skill hands off the bulk extraction to the right tool, then runs the QA layer on what comes back.
Before you hand off: try 
tabular-review
first (
/corporate-legal:tabular-review
). For anything the user's environment can handle — a few hundred documents, a defined column schema — native tabular review is faster to set up, has no per-document cost, and keeps the work product local. Hand off to Luminance/Kira when the corpus is genuinely too large, the team already has a license and workflow, or the matter requires a tool with a validated provenance chain.
Luminance和Kira擅长一件事：读取500份合同并找出每一项控制权变更（CoC）条款。但它们在判断方面表现欠佳——比如判断某一特定CoC条款是否真的适用于当前交易结构。
本技能将批量提取工作移交至合适的工具，然后对返回结果执行QA层检查。
移交前注意事项：优先尝试使用
tabular-review
（
/corporate-legal:tabular-review
）。对于用户环境可处理的任务——几百份文档、定义好的列 schema——原生表格化审查设置更快，无单文档成本，且工作成果保存在本地。仅当文档集确实过大、团队已拥有相关工具许可证和工作流，或事项需要具备可验证溯源链的工具时，才移交至Luminance/Kira。

Load context

加载上下文

~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md
→ AI-assisted review:
  • Tool in use (Luminance / Kira / none)
  • What it's used for (which clause types)
  • Trust level (use as-is / spot-check / full re-review)
  • Handoff process (who loads, who QAs)
If 
~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md
says no AI tool → this skill is a no-op. Everything goes through diligence-issue-extraction directly.
~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md
→ AI辅助审查：
  • 使用的工具（Luminance / Kira / 无）
  • 工具用途（针对哪些条款类型）
  • 信任级别（直接使用 / 抽查 / 全面重新审查）
  • 移交流程（谁负责加载，谁负责QA）
如果
~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md
显示未使用AI工具→本技能不生效。所有工作直接通过尽职调查问题提取流程处理。

When to hand off

移交时机

Hand off when all of:
  • Category has >50 documents (below that, faster to just read them)
  • Extraction target is a clause type the tool is good at (CoC, assignment, exclusivity, MFN, termination, auto-renewal)
  • Documents are reasonably uniform (all customer contracts on similar paper — not a mix of contracts, letters, and board minutes)
Don't hand off:
  • Bespoke or heavily negotiated documents
  • Side letters and amendments (context-dependent, tools miss the interaction with the main agreement)
  • Anything where the question is "what does this mean for the deal" not "does this clause exist"
满足以下所有条件时进行移交：
  • 类别包含超过50份文档（低于此数量，直接人工读取更快）
  • 提取目标为工具擅长的条款类型（CoC、转让、排他性、最惠国待遇（MFN）、终止、自动续约）
  • 文档格式相对统一（均为类似模板的客户合同——而非合同、信函和董事会纪要的混合）
以下情况不移交：
  • 定制化或经过深度谈判的文档
  • 附函和修正案（依赖上下文，工具会遗漏与主协议的关联）
  • 任何需要判断“这对交易意味着什么”而非“该条款是否存在”的任务

The handoff

移交流程

Step 1: Prepare the batch

步骤1：准备批次

  • Identify documents for the batch (from VDR inventory)
  • Specify extraction targets per 
    ~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md
    (which clause types)
  • Note the materiality threshold so tool output can be filtered
  • 确定批次中的文档（来自VDR清单）
  • 根据
    ~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md
    指定提取目标（哪些条款类型）
  • 记录重要性阈值，以便过滤工具输出

Step 2: Load (or instruct the loader)

步骤2：加载（或指导加载人员）

Per 
~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md
— who loads. If it's you, generate the load instructions. If it's someone else, generate the request:
markdown
undefined
根据
~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md
确定负责加载的人员。如果是你，生成加载说明；如果是其他人，生成请求：
markdown
undefined

[Tool] Load Request — [Deal code] — [Category]

[Tool] Load Request — [Deal code] — [Category]

Documents: [N] docs from VDR folder [path] Load to: [Tool workspace/matter] Extraction targets:
  • Change of control / assignment
  • Exclusivity
  • [etc. per 
    ~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md
    ]
Filter output: Flag only where extraction target is present — no need for "no CoC clause found" for every doc.
Return by: [date]
undefined
Documents: [N] docs from VDR folder [path] Load to: [Tool workspace/matter] Extraction targets:
  • Change of control / assignment
  • Exclusivity
  • [etc. per 
    ~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md
    ]
Filter output: Flag only where extraction target is present — no need for "no CoC clause found" for every doc.
Return by: [date]
undefined

Step 3: QA the output

步骤3：输出QA检查

When the tool returns results, apply the trust level:
"Use as-is": Ingest directly into diligence findings. (Only if 
~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md
says this — it's rare.)
"Spot-check X%": Randomly sample X% of flagged documents. For each, read the actual clause and compare to the tool's extraction. If error rate is low, accept the batch. If errors found, widen the sample.
"Full human review of flagged": Tool narrows the universe (500 docs → 80 with CoC clauses). Human reads all 80. Tool saved the time of reading the 420 clean ones.
工具返回结果后，应用信任级别：
“直接使用”：直接导入尽职调查结果。（仅当
~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md
如此规定时使用——这种情况很少见。）
“抽查X%”：随机抽取X%的标记文档。逐一读取实际条款并与工具提取结果对比。如果错误率低，则接受该批次；如果发现错误，则扩大抽样范围。
“对标记内容进行全面人工审查”：工具缩小审查范围（500份文档→80份含CoC条款的文档）。人工读取全部80份。工具节省了读取420份无问题文档的时间。

Step 4: Judgment layer

步骤4：判断层

The tool found the clauses. Now apply judgment:
For each flagged CoC provision: is it actually triggered by this deal?
  • Stock sale vs. asset sale vs. merger — different triggers
  • "Change of control" defined how in the contract — majority ownership? board control? something else?
  • Is there a carve-out for this type of transaction?
This is the part the tool can't do. Output goes to diligence findings in house format.
工具已找到条款。现在需进行判断：
对于每一项标记的CoC条款：它是否真的适用于当前交易？
  • 股票出售 vs 资产出售 vs 合并——触发条件不同
  • 合同中如何定义“控制权变更”——多数股权？董事会控制权？其他定义？
  • 针对此类交易是否存在例外条款？
这是工具无法完成的部分。输出结果需按照内部格式导入尽职调查结果。

Output

输出

The QA summary below is derived from VDR documents that are privileged, confidential, or both. It inherits the sources' privilege and confidentiality status — distribution beyond the privilege circle can waive privilege. Store with the matter's privileged files.
markdown
undefined
以下QA摘要源自具有保密特权或机密性的VDR文档。它继承了源文档的特权和保密状态——超出特权范围分发可能会丧失特权。请与事项的特权文件一同存储。
markdown
undefined

AI Tool Handoff Summary — [Category]

AI Tool Handoff Summary — [Category]

Tool: [Luminance / Kira] Documents processed: [N] Extraction targets: [clause types]
Tool: [Luminance / Kira] Documents processed: [N] Extraction targets: [clause types]

QA

QA

Trust level: [per 
~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md
] Sample size: [N] docs spot-checked Error rate: [X]% — [Accepted / Widened sample / Full re-review triggered]
Trust level: [per 
~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md
] Sample size: [N] docs spot-checked Error rate: [X]% — [Accepted / Widened sample / Full re-review triggered]

Results

Results

Clause typeDocs flaggedAfter judgment layerMaterial
Change of control[N][N actually triggered by deal structure][N above threshold]
Assignment[N][N][N]
→ [N] findings added to diligence issues → [N] consents added to closing checklist
undefined
Clause typeDocs flaggedAfter judgment layerMaterial
Change of control[N][N actually triggered by deal structure][N above threshold]
Assignment[N][N][N]
→ [N] findings added to diligence issues → [N] consents added to closing checklist
undefined

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

本技能不执行的操作

  • It doesn't run Luminance or Kira — it manages the handoff and QA. A human (or the tool's own interface) runs the extraction.
  • It doesn't replace the tool's output with its own judgment entirely — if 
    ~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md
    says spot-check 10%, check 10%, not 100%.
  • It doesn't decide the trust level — that's in 
    ~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md
    , set at cold-start based on the team's experience with the tool.
  • 不直接运行Luminance或Kira——仅管理移交和QA流程。提取操作由人工（或工具自身界面）执行。
  • 不会完全用自身判断替代工具输出——如果
    ~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md
    要求抽查10%，则仅抽查10%，而非100%。
  • 不决定信任级别——该级别在
    ~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md
    中设置，基于团队对工具的使用经验在初始阶段确定。