Back to Details

matter-intake

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

/matter-intake

/matter-intake

  1. Load 
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    → risk calibration (for triage), landscape (for context, conflicts method), stakeholders (for who to loop in).
  2. Follow the workflow and reference below.
  3. Run the uniform intake: identification, conflicts check, source, risk triage, materiality, outside counsel, internal owners, legal hold, key dates, initial posture.
  4. Generate slug from matter name (lowercase, hyphens, year).
  5. Create 
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md
    — full narrative intake.
  6. Create 
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md
    — seeded with the intake as the first entry.
  7. Append structured row to 
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml
    .
  8. Confirm with the user: "Here's the row I'll write — any edits?"
  1. 加载
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    → 风险校准（用于分级）、事务背景（冲突排查方法）、利益相关方（确定需纳入的人员）。
  2. 遵循以下工作流程并参考相关内容。
  3. 执行统一接收流程：身份识别、冲突排查、事务来源、风险分级、重要性评估、外部律师对接、内部负责人指定、法律保留、关键日期、初始立场。
  4. 根据事务名称生成slug（小写字母、连字符、年份后缀）。
  5. 创建
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md
    文件——包含完整的事务接收叙事内容。
  6. 创建
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md
    文件——以本次接收内容作为第一条记录初始化。
  7. 在
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml
    中追加结构化记录行。
  8. 与用户确认：“这是我将写入的记录行——是否需要修改？”

Matter Intake

法律事务接收

Purpose

目的

Every new matter goes through the same intake so the portfolio stays comparable. Uniform rows in 
_log.yaml
let the status skill roll up. Narrative in 
matter.md
captures what the row can't. History file seeded here becomes the event record.
每一项新事务都需经过相同的接收流程，确保事务组合的可比性。
_log.yaml
中的统一记录行可支持状态技能汇总信息。
matter.md
中的叙事内容可记录记录行无法涵盖的细节。在此初始化的历史文件将作为事件记录档案。

Load context

加载上下文

  • ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    — risk calibration (triage thresholds, materiality, settlement ladder), landscape (stakeholders, outside counsel bench).
  • ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml
    — to confirm slug uniqueness.
  • ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    — 风险校准（分级阈值、重要性评估、和解阶梯）、事务背景（利益相关方、外部律师资源）。
  • ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml
    — 确认slug的唯一性。

The intake

接收流程

1. Identification

1. 身份识别

  • Matter name (as commonly referenced, e.g., "Acme v. Us 2026")
  • Counterparty
  • Matter type: 
    contract | employment | ip | regulatory | investigation | product | other
  • Our role: 
    plaintiff | defendant | claimant | respondent | investigated
    • If the practice profile's 
      ## Side
      is 
      plaintiff
      , 
      defense
      , or a "both — default X" variant, pre-fill the role from that default and confirm. If 
      ## Side
      is 
      varies by matter
      , ask cold. Never silently assume a posture the practice profile hasn't set.
    • The role drives downstream skills: plaintiff-posture matters route risk triage to case value / contingency economics; defense-posture matters route to exposure / reserves / insurance tender.
  • Jurisdiction (court, arbitration forum, or regulatory body)
  • 事务名称（通用表述，例如“Acme v. Us 2026”）
  • 对方当事人
  • 事务类型：
    contract | employment | ip | regulatory | investigation | product | other
    （合同|劳动|知识产权|监管|调查|产品|其他）
  • 我方角色：
    plaintiff | defendant | claimant | respondent | investigated
    （原告|被告|索赔方|应诉方|被调查方）
    • 如果业务档案中的
      ## Side
      为
      plaintiff
      、
      defense
      或“两者皆可——默认X”变体，则根据默认值预填角色并确认。如果
      ## Side
      为“因事务而异”，则直接询问。切勿默认业务档案未设定的立场。
    • 我方角色将决定后续技能路径：原告立场事务的风险分级将指向案件价值/ contingency economics（ contingency费用模式）；被告立场事务的风险分级将指向风险敞口/准备金/保险提交。
  • 管辖机构（法院、仲裁机构或监管部门）

2. Conflicts check

2. 冲突排查

Before going further, run the conflicts step per 
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
→ Conflicts clearance.
  • Status: 
    cleared | pending | not-run | waived
  • Method: match what 
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    declares (
    corporate-legal | outside-counsel | system-check | informal | other
    ). If the declared method is 
    informal
    , say so — the record still captures that a counsel's-judgment check was the basis.
  • Cleared by: name / team / firm
  • Cleared date: YYYY-MM-DD
  • Checked against: brief list of the specific names/entities run (counterparty, known affiliates, adverse counsel if known, key witnesses). Thin is fine; "no" is not.
  • Notes: anything flagged but cleared (e.g., "Smith on our board sat on counterparty's board 2019–2021 — cleared as non-overlapping to this matter").
Behavior by status:
  • cleared
    → proceed.
  • pending
    → proceed with intake; flag prominently in 
    matter.md
    and in the log row that conflicts are outstanding; surface again on every 
    /matter-update
    and in 
    /portfolio-status
    until resolved.
  • waived
    → rare; requires a conflict-waiver rationale (writing the waiver is outside this skill — capture that one exists, who signed it, and where it lives).
  • not-run
    → STOP. This is a gate. The skill will not create 
    matter.md
    , 
    history.md
    , or a 
    _log.yaml
    entry until the conflicts posture is resolved. Three acceptable paths:
    Path 1 — Run conflicts now. Pause this intake. Clear per 
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    Conflicts clearance. Return with 
    status: cleared
    or 
    status: waived
    with rationale.
    Path 2 — Mark pending with owner + due date. Allowed only when 
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    Conflicts clearance declares parallel-intake acceptable. Capture: who is running conflicts, when they're expected to return, what entities they're checking. Intake proceeds; matter row carries 
    conflicts.status: pending
    ; 
    /portfolio-status
    flags it every run; 
    /matter-update
    re-prompts until resolved.
    Path 3 — Bypass with documented rationale. Only if the user explicitly acknowledges the bypass. Record in 
    conflicts.override
    :
    yaml
    conflicts:
  status: not-run               # preserved as-is
  override:
    by: [user name]
    date: [YYYY-MM-DD]
    rationale: [why conflicts were bypassed — permanent record; does not auto-expire]
    This field is visible in every 
    /portfolio-status
    , every 
    /matter
    briefing, and every 
    /matter-update
    until removed. It is never removed by the skill — only by explicit user edit to 
    _log.yaml
    after conflicts are actually cleared.
    Do not proceed silently. "I'll do it later" is not an acceptable response. One of Path 1/2/3 must be chosen, and the choice is captured in the record.
This step is not about the skill deciding whether a conflict exists — that's the user's/firm's judgment. It's about making sure the check happened and the record reflects it.
在继续流程前，按照
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
→ 冲突排查流程执行冲突检查步骤。
  • 状态： 
    cleared | pending | not-run | waived
    （已通过|待处理|未执行|已豁免）
  • 方法： 匹配
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    中声明的方法（
    corporate-legal | outside-counsel | system-check | informal | other
    ——公司法务|外部律师|系统检查|非正式检查|其他）。如果声明的方法为
    informal
    ，需如实记录——档案仍需体现该检查基于律师判断。
  • 排查人： 姓名/团队/律所
  • 排查日期： YYYY-MM-DD
  • 排查对象： 简要列出具体检查的名称/实体（对方当事人、已知关联方、已知对方律师、关键证人）。内容简洁即可；不可留空。
  • 备注： 任何已排查但已通过的问题（例如“我方董事会成员Smith曾于2019–2021年担任对方董事会成员——因与本次事务无重叠，已通过排查”）。
不同状态的处理逻辑：
  • cleared
    → 继续流程。
  • pending
    → 继续接收流程；在
    matter.md
    和记录行中显著标记冲突待处理；在每次
    /matter-update
    和
    /portfolio-status
    中再次提示，直至问题解决。
  • waived
    → 罕见情况；需记录冲突豁免理由（撰写豁免文件不属于本技能范畴——仅需记录存在豁免文件、签署人及存储位置）。
  • not-run
    → 停止流程。这是必经关卡。 在冲突状态解决前，本技能不会创建
    matter.md
    、
    history.md
    或
    _log.yaml
    记录。有三种可接受的处理路径：
    路径1——立即执行冲突排查。 暂停本次接收流程。按照
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    的冲突排查流程完成检查。返回
    status: cleared
    或附带理由的
    status: waived
    。
    路径2——标记为待处理并记录负责人+截止日期。 仅当
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    的冲突排查流程允许并行接收时才可使用。记录：谁执行冲突排查、预计完成时间、检查的实体。接收流程继续；事务记录行标记
    conflicts.status: pending
    ；每次
    /portfolio-status
    都会标记该事务；
    /matter-update
    会持续提示直至问题解决。
    路径3——记录理由后绕过排查。 仅当用户明确确认绕过排查时才可使用。在
    conflicts.override
    中记录：
    yaml
    conflicts:
  status: not-run               # 保持原样
  override:
    by: [用户姓名]
    date: [YYYY-MM-DD]
    rationale: [绕过冲突排查的理由——永久记录；不会自动失效]
    该字段会在每次
    /portfolio-status
    、
    /matter
    简报和
    /matter-update
    中显示，直至被手动移除。本技能不会自动移除该字段——仅当冲突排查实际完成后，用户通过编辑
    _log.yaml
    可手动移除。
    不得静默继续流程。“我稍后再处理”不属于可接受的回应。必须选择路径1/2/3中的一种，并将选择记录在档案中。
本步骤并非由技能判断是否存在冲突——这是用户/律所的判断范畴。本步骤仅确保排查已执行，并在档案中如实记录结果。

3. Source

3. 事务来源

How did this arrive?
  • demand-letter | complaint-served | subpoena | regulator-inquiry | internal-report | pre-suit-threat
  • Seed doc opportunity: "If you have the initiating document (complaint, demand, subpoena), attach or share the path. It sharpens the intake."
事务如何发起？
  • demand-letter | complaint-served | subpoena | regulator-inquiry | internal-report | pre-suit-threat
    （索赔函|起诉状送达|传票|监管问询|内部报告|诉讼前威胁）
  • 初始文档收集提示：“如果您有发起文件（起诉状、索赔函、传票），请附上或提供文件路径。这将优化接收流程的准确性。”

4. Risk triage — against house calibration

4. 风险分级——对照内部校准标准

  • Severity: high | medium | low (reference the 
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    severity bands)
  • Likelihood: high | medium | low (reference the 
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    likelihood bands)
  • Resulting risk rating (per the matrix): high | medium | low | critical
  • Damages exposure range (best estimate)
  • Non-monetary exposure (injunction? consent decree? publicity? precedent?)
If the risk calibration in 
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
is thin, don't fake precision. Use the user's gut and note the thinness.
  • 严重程度：高|中|低（参考
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    中的严重程度区间）
  • 发生概率：高|中|低（参考
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    中的概率区间）
  • 最终风险评级（根据矩阵）：高|中|低|极高
  • 损失敞口范围（最佳估算）
  • 非金钱损失（禁令？同意令？公众舆论？先例影响？）
如果
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
中的风险校准标准不够详细，切勿强行精确分级。可参考用户的经验判断，并记录标准不足的情况。

5. Materiality

5. 重要性评估

Against the house thresholds in 
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
:
  • reserved | disclosed | monitored | none
  • If 
    reserved
    : reserve amount and whether finance has been notified
  • If 
    disclosed
    : filing and footnote location
对照
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
中的内部阈值：
  • reserved | disclosed | monitored | none
    （计提准备金|披露|监控|无）
  • 如果为
    reserved
    ：记录准备金金额及是否已通知财务部门
  • 如果为
    disclosed
    ：记录披露文件及附注位置

6. Outside counsel

6. 外部律师对接

  • Firm
  • Lead partner
  • Lead partner email (used by 
    /oc-status
    to draft status requests)
  • Engagement letter status: 
    signed | pending | none
  • Budget authorization: amount and approver
  • Seed doc opportunity: "Engagement letter path, if signed."
If risk is medium or higher and no outside counsel is assigned — flag it.
  • 律所名称
  • 牵头合伙人
  • 牵头合伙人邮箱（供
    /oc-status
    功能生成状态请求邮件）
  • 委托协议状态：
    signed | pending | none
    （已签署|待签署|无）
  • 预算授权：金额及审批人
  • 初始文档收集提示：“如果委托协议已签署，请提供文件路径。”
如果风险评级为中或高且未指定外部律师——需标记提醒。

7. Internal owners

7. 内部负责人

From 
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
landscape — which internal stakeholders are involved?
  • Business lead
  • HR partner (if employment)
  • Comms contact (if reputational risk)
  • CISO (if data or cyber)
  • Other
根据
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
中的事务背景——确定涉及的内部利益相关方：
  • 业务负责人
  • HR合作伙伴（如为劳动事务）
  • 公关联系人（如存在声誉风险）
  • CISO（如涉及数据或网络安全）
  • 其他人员

8. Legal hold

8. 法律保留

  • Issued? If yes: date, scope, custodians (list of names).
  • Next refresh date (default: six months from issuance; adjust per matter).
  • If no and this is active litigation or reasonably anticipated: flag urgently; offer to run 
    /litigation-legal:legal-hold [slug] --issue
    after intake completes.
  • Seed doc opportunity: "Hold notice, if issued."
  • 是否已发出保留通知？如果是：记录日期、范围、保管人（姓名列表）。
  • 下次更新日期（默认：发出后六个月；可根据事务调整）。
  • 如果未发出且事务处于活跃诉讼阶段或可合理预期诉讼——需紧急标记；在接收流程完成后，可提议执行
    /litigation-legal:legal-hold [slug] --issue
    功能。
  • 初始文档收集提示：“如果已发出保留通知，请提供文件路径。”

9. Key dates

9. 关键日期

  • Response deadline (answer, objection, opposition)
  • Next hearing / conference
  • Statute of limitations cutoff (if applicable)
  • Any regulatory deadlines
  • 回应截止日期（答辩、异议、抗辩）
  • 下次听证会/会议日期
  • 诉讼时效截止日期（如适用）
  • 任何监管截止日期

10. Initial posture

10. 初始立场

One-paragraph theory:
  • What's our story?
  • What's theirs?
  • What's the pivot fact?
  • Initial posture: 
    fight | settle | investigate | wait
一段式理论阐述：
  • 我方主张是什么？
  • 对方主张是什么？
  • 核心争议事实是什么？
  • 初始立场：
    fight | settle | investigate | wait
    （抗辩|和解|调查|观望）

Writing the outputs

输出文件撰写

Slug

Slug规则

Lowercase, hyphens, year at the end. Examples: 
acme-v-us-2026
, 
employment-smith-2026
, 
ftc-inquiry-2026
.
Confirm slug is unique in 
_log.yaml
before writing.
小写字母、连字符分隔、末尾加年份。示例：
acme-v-us-2026
、
employment-smith-2026
、
ftc-inquiry-2026
。
撰写前需确认slug在
_log.yaml
中唯一。

~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md

~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md

markdown
[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]
markdown
[工作成果页眉——根据插件配置## Outputs——因角色而异；详见`## Who's using this`]

[Matter Name]

[事务名称]

Slug: [slug] Opened: [YYYY-MM-DD] Our role: [plaintiff/defendant/etc.] Status: [status]
Slug: [slug] 创建日期: [YYYY-MM-DD] 我方角色: [原告/被告等] 状态: [状态]

Identification

身份识别

[counterparty, jurisdiction, matter type, source]
[对方当事人、管辖机构、事务类型、来源]

Conflicts

冲突排查

Status: [cleared / pending / not-run / waived] Method: [corporate-legal / outside-counsel / system-check / informal / other] Cleared by: [name] Cleared date: [YYYY-MM-DD] Checked against: [entities run] Notes: [any flags cleared, waiver reference if applicable]
状态: [已通过/待处理/未执行/已豁免] 方法: [公司法务/外部律师/系统检查/非正式检查/其他] 排查人: [姓名] 排查日期: [YYYY-MM-DD] 排查对象: [检查的实体] 备注: [任何已通过的问题标记、豁免文件参考（如适用）]

Risk triage

风险分级

Severity: [band] — [why, with reference to house severity definitions] Likelihood: [band] — [why] Risk rating: [high/medium/low/critical] Exposure: [dollar range + non-monetary]
严重程度: [区间] — [理由，参考内部严重程度定义] 发生概率: [区间] — [理由] 风险评级: [高/中/低/极高] 风险敞口: [金额范围 + 非金钱损失]

Materiality

重要性评估

[reserved/disclosed/monitored/none — with reserve amount, disclosure location, or reasoning if "none"]
[计提准备金/披露/监控/无——如为计提准备金需记录金额，如为披露需记录位置，如为“无”需记录理由]

Outside counsel

外部律师对接

[firm, lead, engagement status, budget]
[律所名称、牵头合伙人、委托状态、预算]

Internal owners

内部负责人

[stakeholders and why each is involved]
[利益相关方及参与理由]

Legal hold

法律保留

[status, date, scope]
[状态、日期、范围]

Key dates

关键日期

[list]
[列表]

Initial theory

初始理论

[one paragraph: our story, their story, pivot fact, initial posture] 
[SME VERIFY — theory at intake is a working hypothesis; confirm with outside counsel before any filing or material communication that assumes this framing]
[一段式内容：我方主张、对方主张、核心争议事实、初始立场] 
[专家验证——接收阶段的理论为工作假设；在任何基于该框架的文件提交或重要沟通前，需与外部律师确认]

Open questions

待澄清问题

[anything not yet known that matters — e.g., "insurance tender pending", "unclear whether we have coverage for X"]
[任何尚未明确但重要的问题——例如“保险提交待处理”“尚不明确我方是否覆盖X事项的保险”]

Seed documents

初始文档

DocPath / pointer
[e.g., complaint][path or "not yet shared"]
undefined
文档路径/指向
[例如：起诉状][路径或“尚未提供”]
undefined

~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md

~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md

Seed the history file with the intake as entry zero:
markdown
undefined
以本次接收内容作为第0条记录初始化历史文件：
markdown
undefined

History: [Matter Name]

历史记录: [事务名称]

Append-only event log. Most recent at top.
仅追加式事件日志。最新记录位于顶部。

[YYYY-MM-DD] — Matter opened

[YYYY-MM-DD] — 事务创建

[Source, who brought it in, initial triage summary, outside counsel assigned, legal hold issued yes/no.]
undefined
[来源、提交人、初始分级摘要、指定的外部律师、是否发出法律保留通知。]
undefined

Append to 
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml

追加至
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml

Add a row per the schema. Example:
yaml
- id: acme-v-us-2026
  name: "Acme Corp v. Company"
  type: contract
  role: defendant
  counterparty: "Acme Corp"
  jurisdiction: "N.D. Cal."
  # status is derived from source:
  #   source: pre-suit-threat | demand-letter           → status: threatened
  #   source: complaint-served | subpoena | regulator-inquiry → status: active
  #   source: internal-report                           → status: threatened (default) or active if formal process has started
  status: active
  stage: pleadings
  source: complaint-served
  outside_counsel:
    firm: "Wilson Sonsini"
    lead: "J. Reyes"
    email: "jreyes@wsgr.example.com"
    engagement: signed
  conflicts:
    status: cleared
    method: corporate-legal
    cleared_by: "K. Patel"
    cleared_date: 2026-04-20
    override:                   # populated only on Path 3 bypass
      by: null
      date: null
      rationale: null
  risk: high
  materiality: reserved
  exposure_range: "$2M–$5M"
  internal_owners:
    business_lead: "Jane Smith"
    hr_partner: null
    comms_contact: null
  legal_hold:
    issued: true
    issued_date: 2026-02-15
    scope: "Sales org 2023–2026"
    custodians: ["Jane Smith", "R. Chen", "T. Patel"]
    last_refresh: 2026-02-15
    next_refresh: 2026-08-15
    released: null
  related_matters: []
  opened: 2026-04-20
  next_deadline: 2026-05-15
  last_updated: 2026-04-20
  path: matters/acme-v-us-2026/
按照 schema 添加一行记录。示例：
yaml
- id: acme-v-us-2026
  name: "Acme Corp v. Company"
  type: contract
  role: defendant
  counterparty: "Acme Corp"
  jurisdiction: "N.D. Cal."
  # 状态由来源推导:
  #   source: pre-suit-threat | demand-letter           → status: threatened
  #   source: complaint-served | subpoena | regulator-inquiry → status: active
  #   source: internal-report                           → status: threatened (默认) 或 active（如已启动正式流程）
  status: active
  stage: pleadings
  source: complaint-served
  outside_counsel:
    firm: "Wilson Sonsini"
    lead: "J. Reyes"
    email: "jreyes@wsgr.example.com"
    engagement: signed
  conflicts:
    status: cleared
    method: corporate-legal
    cleared_by: "K. Patel"
    cleared_date: 2026-04-20
    override:                   # 仅在路径3绕过排查时填充
      by: null
      date: null
      rationale: null
  risk: high
  materiality: reserved
  exposure_range: "$2M–$5M"
  internal_owners:
    business_lead: "Jane Smith"
    hr_partner: null
    comms_contact: null
  legal_hold:
    issued: true
    issued_date: 2026-02-15
    scope: "Sales org 2023–2026"
    custodians: ["Jane Smith", "R. Chen", "T. Patel"]
    last_refresh: 2026-02-15
    next_refresh: 2026-08-15
    released: null
  related_matters: []
  opened: 2026-04-20
  next_deadline: 2026-05-15
  last_updated: 2026-04-20
  path: matters/acme-v-us-2026/

Confirm before writing

撰写前确认

Show the user the row and the matter.md content:
Here's what I'll write. Flag anything wrong or thin before I commit.
向用户展示记录行和matter.md内容：
这是我将写入的内容。在我提交前，请标记任何错误或不完善的地方。

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

本技能不执行的操作

  • Run the conflicts check itself. It records the result, status, method, and the entities checked. The actual clearance happens in whatever system (or judgment) the house practice profile declares. If the user says "cleared," the skill takes that at face value and captures the metadata.
  • Decide the initial theory. It captures what the user says; it doesn't invent one.
  • Issue the legal hold. Flags it if missing. User issues it.
  • 自行执行冲突排查。 仅记录结果、状态、方法及检查的实体。实际排查需按照内部业务档案声明的系统（或判断流程）执行。如果用户表示“已通过”，本技能将如实记录并保存元数据。
  • 决定初始理论。仅记录用户表述的内容；不会自行创建理论。
  • 发出法律保留通知。仅在未发出时标记提醒。由用户执行通知发出操作。