closing-checklist
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese/closing-checklist
/closing-checklist
- Read and use the modes below.
~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/closing-checklist.yaml - If status update provided: Mode 3 (update item).
- Otherwise Mode 4: blocking items, critical path, days to close.
- 读取并使用以下模式。
~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/closing-checklist.yaml - 如果提供了状态更新:使用模式3(更新事项)。
- 否则使用模式4:查看阻碍事项、关键路径和剩余交割天数。
Matter context
事项上下文
Matter context. Check in the practice-level CLAUDE.md. If 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 or say ." Load the active matter's for matter-specific context and overrides. Write outputs to the matter folder at . Never read another matter's files unless is .
## Matter workspacesEnabled✗/corporate-legal:matter-workspace switch <slug>practice-levelmatter.md~/.claude/plugins/config/claude-for-legal/corporate-legal/matters/<matter-slug>/Cross-matter contexton事项上下文。查看业务级CLAUDE.md中的。如果为(内部用户默认设置),则跳过本段剩余内容——技能使用业务级上下文,事项机制不可见。如果已启用且没有活跃事项,请询问:“这是针对哪个事项的?运行或选择(业务级)。”加载活跃事项的以获取特定于事项的上下文和覆盖配置。将输出写入事项文件夹。除非(跨事项上下文)开启,否则切勿读取其他事项的文件。
## Matter workspacesEnabled✗/corporate-legal:matter-workspace switch <slug>practice-levelmatter.md~/.claude/plugins/config/claude-for-legal/corporate-legal/matters/<matter-slug>/Cross-matter contextPurpose
用途
Deals close when the checklist is done. Everything on it, done. Nothing missing. This skill maintains the list, ingests new items as they surface from diligence, and tells the team what's blocking.
当清单上的所有事项都完成且无遗漏时,交易即可交割。本技能负责维护清单,从尽职调查中导入新出现的事项,并告知团队哪些因素在阻碍交割。
The checklist
交割清单
Lives at . Structure:
~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/closing-checklist.yamlyaml
deal_code: "Project Falcon"
target_close: [DATE]
signing_date: [DATE]
last_updated: [DATE]
conditions_precedent:
- id: CP-001
item: "HSR waiting period expiration"
category: "Regulatory"
responsible: "Buyer counsel"
due: 2026-04-15
status: "Filed 2026-03-01, waiting period runs"
blocking: true
source: "Purchase Agreement §7.1(a)"
- id: CP-002
item: "Acme Corp consent to assignment"
category: "Third-party consents"
responsible: "Target — Jane Doe"
due: 2026-04-20
status: "Request sent 2026-03-10, no response"
blocking: true
source: "Schedule 3.12(a)(4); Acme MSA §14.2"
closing_deliverables:
- id: CD-001
item: "Certificate of good standing — Target (DE)"
category: "Corporate"
responsible: "Target counsel"
due: 2026-04-28
status: "Not started"
blocking: true
source: "Purchase Agreement §2.3(b)(iv)"
# ... etc存储于。结构如下:
~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/closing-checklist.yamlyaml
deal_code: "Project Falcon"
target_close: [DATE]
signing_date: [DATE]
last_updated: [DATE]
conditions_precedent:
- id: CP-001
item: "HSR waiting period expiration"
category: "Regulatory"
responsible: "Buyer counsel"
due: 2026-04-15
status: "Filed 2026-03-01, waiting period runs"
blocking: true
source: "Purchase Agreement §7.1(a)"
- id: CP-002
item: "Acme Corp consent to assignment"
category: "Third-party consents"
responsible: "Target — Jane Doe"
due: 2026-04-20
status: "Request sent 2026-03-10, no response"
blocking: true
source: "Schedule 3.12(a)(4); Acme MSA §14.2"
closing_deliverables:
- id: CD-001
item: "Certificate of good standing — Target (DE)"
category: "Corporate"
responsible: "Target counsel"
due: 2026-04-28
status: "Not started"
blocking: true
source: "Purchase Agreement §2.3(b)(iv)"
# ... etcModes
模式
Mode 1: Initialize from the purchase agreement
模式1:从采购协议初始化
Read the signed (or near-final) purchase agreement. Extract:
- Every condition precedent (location varies by agreement — read the actual section headings)
- Every closing deliverable (closing deliverables schedule or corresponding section)
- Every covenant with a pre-closing deadline
Each becomes a checklist item with a source cite to the agreement section.
Research obligations before populating regulatory/approval items. Antitrust, foreign-investment, and sector-specific approvals (for example, HSR-style filings, CFIUS, industry regulators) have jurisdiction-specific mechanics, thresholds, and timing windows that change. Extract the name of each regulatory condition from the PA, then research the currently operative mechanics (who files, when, what triggers a second request, what the waiting period is). Cite primary sources and verify currency. Do not populate a timing assumption from memory.
Material-adverse-effect / material-adverse-change closing conditions. Pull the defined term from the PA — MAC/MAE framing is negotiated, not a standard. Research the governing-law interpretation of the specific language used (Delaware, New York, and other jurisdictions treat carve-outs and quantitative tests differently) before flagging an event as a potential MAC trigger.
Consent-requirement extraction from material contracts depends on governing-law default rules and the specific anti-assignment language in each contract. Research the applicable rule per contract rather than assuming a default.
读取已签署(或接近最终版本)的采购协议,提取:
- 所有先决条件(位置因协议而异——需阅读实际章节标题)
- 所有交割交付物(交割交付物附表或对应章节)
- 所有带有交割前截止日期的契约
每一项都成为清单中的一个事项,并标注协议章节的来源引用。
填充监管/审批事项前需研究相关义务。反垄断、外国投资和特定行业审批(例如HSR式申报、CFIUS、行业监管机构)具有司法管辖区特定的机制、门槛和时间窗口,且会发生变化。从采购协议中提取每个监管条件的名称,然后研究当前生效的机制(申报方、申报时间、触发二次请求的条件、等待期时长)。引用主要来源并验证时效性。切勿凭记忆填充时间假设。
重大不利影响/重大不利变化交割条件。从采购协议中提取定义术语——MAC/MAE的表述是协商确定的,并非标准条款。在将某一事件标记为潜在MAC触发因素之前,需研究管辖法律对所用特定语言的解释(特拉华州、纽约州和其他司法管辖区对例外情形和量化测试的处理方式不同)。
从重要合同中提取同意要求取决于管辖法律的默认规则和每份合同中的特定反转让条款。需针对每份合同研究适用规则,而非假设默认情况。
Mode 2: Ingest from diligence (the "self-updating" part)
模式2:从尽职调查中导入(“自动更新”部分)
Mode 2 is triggered when an upstream skill produces a finding with a pre-closing action. The upstream skills and output types this mode ingests:
- findings — any finding flagged for a closing action (consent, shareholder vote, board resolution, regulatory filing, release, escrow mechanic, pay-off letter). Not just "consents" — see the extraction skill's Handoffs section for the full list.
diligence-issue-extraction - CoC / assignment items — change-of-control provisions, anti-assignment clauses, MFN triggers surfaced during schedule build.
material-contract-schedule - output — the exec-tier brief aggregates extraction findings and sometimes surfaces a closing-action item that a mechanical read of the individual extraction memos would miss (e.g., a §280G cleansing vote rolled up across multiple employment agreements, or a composite consent package). Mode 2 reads the latest deal-team-summary in the deal folder and reconciles its closing-action items against the checklist. Anything flagged by deal-team-summary as requiring pre-closing action that is not already on the checklist is appended.
deal-team-summary
The handoff schema covers the full range of pre-closing actions, not just consents:
yaml
handoff:
# Required fields
item: "[Counterparty or action, one line]"
category: "[Third-party consents | Shareholder / board action | Regulatory filing | Release / termination | Escrow / holdback | Closing deliverable]"
source: "[Contract name / statutory section / VDR path + Bates]"
blocking: true # unless the agreement has a materiality qualifier
severity: "[🔴 / 🟠 / 🟡 / 🟢 — carried from upstream, see severity-floor rule in CLAUDE.md]"
# Consent / third-party action fields
counterparty: "[e.g., Dunmore Holdings LLC]"
guarantor: "[e.g., Buyer parent guaranty required, or N/A]"
conditions: "[any substantive condition the counterparty attached — e.g., 'replacement guaranty from buyer parent required before consent effective']"
notice_deadline: "[e.g., 30 days prior to closing, or specific date]"
# Corporate action fields
approval_body: "[Shareholders | Board | Committee | Regulator]"
approval_threshold: "[e.g., 75% disinterested stockholder vote for §280G cleansing]"
statutory_or_charter_source: "[e.g., IRC §280G(b)(5)(B); Charter Art. IV §2]"
# Timing
estimated_time_to_complete: "[e.g., 30 days]"
must_occur_before: "[e.g., closing | signing | end of hiatus period]"Preserve every field the upstream skill populated. A "Dunmore consent required, with replacement guaranty condition and 30-day notice" should surface on the checklist with all three elements (consent, guarantor, notice), not collapse to "Dunmore consent to change of control." When the upstream skill provides a severity, carry it — see the cross-skill severity floor rule in .
~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.mdAppend to the checklist. De-dupe on (counterparty + action type), not on the freeform item name — a Dunmore consent and a Dunmore release are different items even though both name Dunmore. When de-duping, merge fields rather than overwrite: if one handoff populated and a later handoff populated , the checklist row carries both.
guarantornotice_deadline当上游技能生成带有交割前行动的调查结果时,触发模式2。本模式导入的上游技能和输出类型包括:
- (尽职调查问题提取)结果——任何标记为需要交割行动的结果(同意、股东投票、董事会决议、监管申报、解除、托管机制、还款函)。不仅限于“同意”——请查看提取技能的“交接”部分以获取完整列表。
diligence-issue-extraction - (重要合同附表)控制权变更/转让事项——在附表构建过程中发现的控制权变更条款、反转让条款、最惠国待遇触发条件。
material-contract-schedule - (交易团队摘要)输出——高管级简报汇总了提取结果,有时会发现单个提取备忘录的机械读取可能遗漏的交割行动事项(例如,跨多个雇佣协议汇总的§280G清洗投票,或综合同意包)。模式2读取交易文件夹中的最新交易团队摘要,并核对其交割行动事项与清单的一致性。任何被交易团队摘要标记为需要交割前行动且尚未在清单中的事项将被追加。
deal-team-summary
交接 schema 涵盖了所有交割前行动,不仅限于同意:
yaml
handoff:
# 必填字段
item: "[交易对手或行动,一行描述]"
category: "[第三方同意 | 股东/董事会行动 | 监管申报 | 解除/终止 | 托管/扣留 | 交割交付物]"
source: "[合同名称/法定章节/VDR路径+Bates编号]"
blocking: true # 除非协议包含实质性限定条件
severity: "[🔴 / 🟠 / 🟡 / 🟢 — 继承自上游技能,详见CLAUDE.md中的严重程度下限规则]"
# 同意/第三方行动字段
counterparty: "[例如:Dunmore Holdings LLC]"
guarantor: "[例如:需买方母公司担保,或不适用]"
conditions: "[交易对手附加的任何实质性条件 — 例如:“生效前需买方母公司提供替代担保”]"
notice_deadline: "[例如:交割前30天,或特定日期]"
# 公司行动字段
approval_body: "[股东 | 董事会 | 委员会 | 监管机构]"
approval_threshold: "[例如:§280G清洗需75%无利害关系股东投票通过]"
statutory_or_charter_source: "[例如:IRC §280G(b)(5)(B); 章程第IV条第2款]"
# 时间安排
estimated_time_to_complete: "[例如:30天]"
must_occur_before: "[例如:交割 | 签署 | 休假期结束]"保留上游技能填充的所有字段。例如“需Dunmore同意,附带替代担保条件和30天通知期限”应完整显示在清单中,包含三个要素(同意、担保人、通知),而非简化为“Dunmore同意控制权变更”。如果上游技能提供了严重程度,则保留该信息——详见中的跨技能严重程度下限规则。
~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md追加到清单中。按(交易对手 + 行动类型)去重,而非按自由格式的事项名称去重——Dunmore同意和Dunmore解除是不同的事项,即使两者都提及Dunmore。去重时合并字段而非覆盖:如果一次交接填充了,后续交接填充了,则清单行应同时包含这两个字段。
guarantornotice_deadlineMode 3: Status update
模式3:状态更新
User (or dataroom-watcher agent) provides a status update. Find the item, update status and last-updated.
/corporate-legal:closing-checklist
CP-002: Acme responded, consent form attached, needs countersignature用户(或数据室监控Agent)提供状态更新。找到对应事项,更新状态和最后更新时间。
/corporate-legal:closing-checklist
CP-002: Acme已回复,附上同意书,需会签Mode 4: What's blocking
模式4:查看阻碍因素
markdown
[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]
> This status report is derived from the purchase agreement, diligence findings, and internal deal records. It inherits their privilege and confidentiality status — distribution beyond the privilege circle (counterparty, broader business teams) can waive privilege. Confirm the distribution list before sending.markdown
[工作产品标题 — 按插件配置## Outputs(输出)设置,因角色而异;详见`## Who's using this`(使用者)]
> 本状态报告源自采购协议、尽职调查结果和内部交易记录。其继承了这些资料的保密特权——向特权圈外(交易对手、更广泛的业务团队)分发可能会丧失特权。发送前请确认分发列表。Closing Checklist Status — [Deal code] — [date]
交割清单状态 — [交易代码] — [日期]
Target close: [date] ([N] days out)
Items: [N] total — [N] done, [N] in progress, [N] not started
目标交割日期: [日期](剩余[N]天)
事项总数: [N]项 — [N]项已完成,[N]项进行中,[N]项未开始
🔴 Blocking and at risk
🔴 阻碍且存在风险
| ID | Item | Due | Status | Days to due |
|---|---|---|---|---|
| [CP-XXX] | [item] | [date] | [status] | [N] |
| ID | 事项 | 截止日期 | 状态 | 剩余天数 |
|---|---|---|---|---|
| [CP-XXX] | [事项] | [日期] | [状态] | [N] |
🟡 Blocking, on track
🟡 阻碍但进展正常
[same table]
[同上表格]
✅ Complete
✅ 已完成
[N] items — [collapsed list]
[N]项 — [折叠列表]
Not blocking (post-closing, informational)
无阻碍(交割后,仅供参考)
[N] items
Critical path: [The item(s) that, if they slip, push the close date]
undefined[N]项
关键路径: [若延误将推迟交割日期的事项]
undefinedCritical path analysis
关键路径分析
Not all blocking items are equal. A consent that takes 30 days to get is critical path. A good-standing certificate that takes 2 days is not, even though both are blocking.
For each blocking item, estimate time-to-complete. The ones where are at risk. Those go at the top of every status report.
(due date - today) < estimated timeIf the checklist has more than ~10 items, or any time the user asks: offer the dashboard (see CLAUDE.md ). Shape the offer for this output — counts by status (done / in progress / not started / at risk), a critical-path view grouped by workstream, and a sortable grid with item, owner, due date, and days-to-due.
## Outputs → Dashboard offer for data-heavy outputs并非所有阻碍事项的重要性都相同。需要30天才能获得的同意属于关键路径,而只需2天即可获取的良好存续证明则不属于,尽管两者都是阻碍因素。
对于每个阻碍事项,估算完成时间。那些的事项存在风险,应放在每份状态报告的顶部。
(截止日期 - 当前日期) < 估算完成时间如果清单包含约10项以上的事项,或任何用户提出请求时:提供仪表板(详见CLAUDE.md中(输出→针对数据密集型输出的仪表板提供))。针对本输出调整提供内容——按状态(已完成/进行中/未开始/存在风险)统计数量,按工作流分组的关键路径视图,以及包含事项、负责人、截止日期和剩余天数的可排序网格。
## Outputs → Dashboard offer for data-heavy outputsIntegration: dataroom-watcher agent
集成:数据室监控Agent
The agent checks the checklist daily, pulls any status updates from email/Slack if connected, and posts the "what's blocking" report to the deal team channel. Mode 4 is the agent's output.
该Agent每日检查清单,如果已连接则从电子邮件/Slack提取任何状态更新,并将“阻碍因素”报告发布到交易团队频道。模式4是该Agent的输出。
Consequential-action gate (certify closing)
重大行动闸门(交割认证)
Before producing a "ready to close / all CPs satisfied" certification or closing memo: Read in . If the Role is Non-lawyer:
## Who's using this~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.mdCertifying that closing conditions have been satisfied (or producing a closing memo asserting this) has legal consequences — it's the signal that drives funds flow and post-closing obligations. Have you reviewed this with an attorney? If yes, proceed. If no, here's a brief to bring to them:
- The full CP list with status (what's done, what's in progress, what's not started)
- Anything where evidence of completion is weak or missing
- Any waivers or side letters needed for items that won't close in time
- Open questions (counterparty consents still pending, any MAC/bring-down risk)
- What to ask the attorney (is this ready to call closed; are any conditions being walked past that shouldn't be; what needs to go on a schedule of exceptions)
If you need to find an attorney, solicitor, barrister, or other authorised legal professional: contact your professional regulator (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) for a referral service.
Do not produce a final "ready to close" certification past this gate without an explicit yes. Status tracking and "what's blocking" reports do not require the gate.
在生成“可交割/所有先决条件已满足”认证或交割备忘录之前: 阅读中的(使用者)部分。如果角色为非律师:
~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md## Who's using this证明交割条件已满足(或生成断言此内容的交割备忘录)具有法律后果——这是驱动资金流动和交割后义务的信号。您是否已与律师审核过此内容?如果是,请继续。如果否,请准备以下内容提交给律师:
- 完整的先决条件列表及状态(已完成、进行中、未开始)
- 任何完成证据薄弱或缺失的事项
- 对于无法按时完成的事项所需的弃权书或附函
- 未解决的问题(交易对手同意仍在等待、任何MAC/交割前风险)
- 需向律师咨询的问题(是否可宣布交割;是否有不应忽略的条件;哪些事项需列入例外附表)
如果您需要寻找律师、事务律师、出庭律师或其他授权法律专业人士:联系您所在司法管辖区的专业监管机构(美国为州律师协会,英格兰和威尔士为SRA/律师标准委员会,苏格兰/北爱尔兰/爱尔兰/加拿大/澳大利亚为律师协会,或其他司法管辖区的对应机构)获取推荐服务。
未经明确同意,请勿通过此闸门生成最终的“可交割”认证。状态跟踪和“阻碍因素”报告无需经过此闸门。
What this skill does not do
本技能不负责的事项
- It doesn't obtain consents, file forms, or draft documents. It tracks that they need to happen.
- It doesn't decide what's blocking — the purchase agreement decides that. This skill reads the agreement.
- It doesn't close the deal. It tells you when you can.
- 不负责获取同意、提交表单或起草文件,仅负责跟踪这些事项的必要性。
- 不决定哪些事项构成阻碍——采购协议对此有规定,本技能仅负责解读协议。
- 不负责完成交易,仅负责告知您何时可以进行交割。",