closing-checklist

/closing-checklist

Read ~/.claude/plugins/config/claude-for-legal-zh/corporate-legal/deals/[代码]/closing-checklist.yaml and use the following patterns.
If there is a status update: pattern 3 (update item).
Otherwise pattern 4: blockers, critical path, days to closing.

Matter context

Matter context. Check the practice-level CLAUDE.md for ## 事项工作区. If Enabled is ✗(the default for corporate legal users), skip the rest of this section—the skill uses practice-level context and the matter mechanism is invisible. If enabled and there is no active matter, ask: "Which matter is this? Run /corporate-legal:matter-workspace switch <事项简称> or say 实务级." Load the active matter's matter.md to get matter-specific context and override rules. Output is written to the matter folder ~/.claude/plugins/config/claude-for-legal-zh/corporate-legal/matters/<事项简称>/. Unless 跨事项上下文 is 开, never read another matter's files.

Purpose

When the checklist is complete, the deal closes. Every item on the list, done. Nothing missed. This skill maintains the list, incorporates new items discovered from due diligence, and tells the team what is blocking.

Checklist

Stored at ~/.claude/plugins/config/claude-for-legal-zh/corporate-legal/deals/[代码]/closing-checklist.yaml. Structure:

deal_code: "Project Falcon"
target_close: [日期]
signing_date: [日期]
last_updated: [日期]

conditions_precedent:
  - id: CP-001
    item: "经营者集中审查等待期届满"
    category: "监管审批"
    responsible: "买方律师"
    due: 2026-04-15
    status: "已于2026-03-01申报，等待期进行中"
    blocking: true
    source: "股权收购协议 §7.1(a)"

  - id: CP-002
    item: "Acme Corp 同意合同转让"
    category: "第三方同意"
    responsible: "目标公司 — 张三"
    due: 2026-04-20
    status: "请求已于2026-03-10发出，无回应"
    blocking: true
    source: "清单 3.12(a)(4)；Acme 主协议 §14.2"

closing_deliverables:
  - id: CD-001
    item: "目标公司存续证明"
    category: "公司"
    responsible: "目标公司律师"
    due: 2026-04-28
    status: "未开始"
    blocking: true
    source: "股权收购协议 §2.3(b)(iv)"

  # ... 等等

Patterns

Pattern 1: Initialize from the equity purchase agreement

Read the signed (or near-final) equity purchase agreement. Extract:

Each closing condition precedent (location varies by agreement—read the actual section headings)
Each closing deliverable (closing deliverables list or the corresponding section)
Each covenant with a pre-closing deadline

Each becomes a checklist item with a source citation to the agreement section.

Research obligation before populating regulatory/approval items. Antitrust, foreign investment, and industry-specific approvals (e.g., merger control filing, foreign investment security review, industry regulator approval) have jurisdiction-specific operational mechanisms, thresholds, and timing windows, and they change. Extract the name of each regulatory condition from the purchase agreement, then research the currently effective operational mechanism (who files, when, what triggers a second review, how long the waiting period is). Cite primary sources and verify timeliness. Do not populate timing assumptions from memory [yuandian检索]。

Material adverse effect/material adverse change closing conditions. Extract the defined terms from the purchase agreement—the material adverse effect/material adverse change wording is a negotiated result, not a standard template. Before marking an event as a possible material adverse effect/material adverse change trigger, research how the specific language used is understood under the governing law (different jurisdictions treat exception clauses and quantitative tests differently).

Extract consent requirements from material contracts Depends on the default rule under the governing law and the specific anti-assignment language in each contract. Research the applicable rule contract by contract rather than assuming a default rule [yuandian检索]。

Pattern 2: Receive from due diligence (the "self-updating" part)

Pattern 2 triggers when an upstream skill produces a finding with a pre-closing action. The upstream skills and output types this pattern receives:

diligence-issue-extraction Finding——Any finding marked as a closing action (consent, shareholder vote, board resolution, regulatory filing, release letter, escrow mechanism, payoff letter). Not just "consent" — see the handoff section of the extraction skill for the full list.
material-contract-schedule Change of control/contract assignment items——Change of control clauses, anti-assignment clauses, most-favored-nation triggers that arise during checklist construction.
deal-team-summary Output——Executive briefing summarizing extracted findings, sometimes surfacing closing action items that a mechanical reading of a single extraction memo would miss (e.g., resolution votes spanning multiple employment contracts, or a combined consent package). Mode 2 reads the latest deal-team-summary in the deal folder and cross-checks the closing action items in it against the checklist. Any item flagged by the deal-team-summary as requiring pre-closing action and not yet on the checklist is appended.

The handoff mode covers all pre-closing actions, not just consents:

handoff:
  # 必填字段
  item: "[对方当事人或行动，一行]"
  category: "[第三方同意 | 股东/董事会行动 | 监管申报 | 解除/终止 | 托管/扣留 | 交割交付物]"
  source: "[合同名称 / 法条章节 / 数据室路径 + 页码]"
  blocking: true  # 除非协议含重大性限定
  severity: "[🔴 / 🟠 / 🟡 / 🟢 — 承自上游，见 CLAUDE.md 中的严重程度下限规则]"

  # 同意/第三方行动字段
  counterparty: "[例如：某某有限公司]"
  guarantor: "[例如：需要买方母公司提供担保，或不适用]"
  conditions: "[对方当事人附加的任何实质性条件——例如'需买方母公司提供替代担保后同意始生效']"
  notice_deadline: "[例如：交割前30天，或具体日期]"

  # 公司行动字段
  approval_body: "[股东会 | 董事会 | 专门委员会 | 监管机构]"
  approval_threshold: "[例如：需经出席会议的股东所持表决权的三分之二以上通过]"
  statutory_or_charter_source: "[例如：《公司法》第120条；公司章程第IV条第2节]"

  # 时间
  estimated_time_to_complete: "[例如：30天]"
  must_occur_before: "[例如：交割 | 签署 | 中断期结束]"

Retain every field populated by the upstream skill. "Consent of so-and-so required, with substitute guarantor condition and 30 days' notice" should show all three elements on the checklist (consent, guarantor, notice), rather than being compressed into "so-and-so change of control consent." When the upstream skill provides a severity level, inherit it — see the cross-skill severity floor rule in CLAUDE.md.

Append to the checklist. Deduplicate by (counterparty + action type), not by free-text item name — a consent for so-and-so and a release for so-and-so are different items, even though both mention so-and-so. When deduplicating, merge without overwriting: if one handoff populated guarantor, and another handoff populated notice_deadline, the checklist row should contain both.

Mode 3: Status Update

The user (or data room monitoring agent) provides a status update. Find the item, update the status and the last updated date.

/corporate-legal:closing-checklist
CP-002: Acme 已回应，同意表格已附，需要副签

Mode 4: What's Blocking

[工作成果页眉 — 按插件配置 ## 输出规范 — 因角色而异；参见 `## 使用者`]

> 本状态报告来源于股权收购协议、尽调发现和内部交易记录。它继承其特权和保密状态——向特权保护圈之外分发（对方当事人、更广泛的业务团队）可能放弃特权。发送前确认分发名单。

## 交割检查表状态 — [交易代码] — [日期]

**目标交割日：**[日期]（距今 [N] 天）
**项目：**[N] 总计 — [N] 已完成，[N] 进行中，[N] 未开始

### 🔴 阻碍且有风险

| ID | 项目 | 截止日 | 状态 | 距截止天数 |
|---|---|---|---|---|
| [CP-XXX] | [项目] | [日期] | [状态] | **[N]** |

### 🟡 阻碍，在轨

[同上表格]

### ✅ 已完成

[N] 项 — [折叠列表]

### 非阻碍（交割后，信息性）

[N] 项

---

**关键路径：** [如该项目延误，将推后交割日期的项目]

Critical path analysis

Not all blockers are equal. A consent that takes 30 days to obtain is on the critical path. A good standing certificate that takes 2 days is not, even though both are blocking.

For each blocker, estimate the time to completion. Any with (截止日 - 今天) < 估计时间 are at risk. These go at the top of every status report.

If the checklist has more than about 10 items, or the user asks at any time: provide a dashboard (see CLAUDE.md ## 输出规范 → 数据密集产出的仪表盘选项). Customize for this output: counts by status (completed/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 date.

Integration: Data Room Monitoring Agent

The agent checks the checklist daily, pulls any status updates from email/Feishu if connected, and pushes the "what's blocking" report to the deal team channel. Mode 4 is the agent's output.

Consequential Action Gate (Certifying Closing)

Before producing a "ready to close/all conditions precedent to closing satisfied" certification or closing memo: Read ~/.claude/plugins/config/claude-for-legal-zh/corporate-legal/CLAUDE.md in ## 使用者. If the role isnon-legal personnel：

Certifying that conditions precedent to closing are satisfied (or issuing a closing memo asserting as much) has legal consequences — it is the signal that moves funds and triggers post-closing obligations. Have you reviewed with a lawyer? If reviewed, proceed. If not reviewed, here is a brief to bring to the lawyer:

Complete list of conditions precedent to closing and their status (which are completed, which are in progress, which are not started)

Any matters where evidence is weak or missing have been completed

Any waivers or supplement letters required for items that cannot be delivered on time

Open issues (counterparty consent still pending, any material adverse effect/material adverse change/representation update risk)

Questions to raise with counsel (whether this can be called for closing; whether any closing conditions are being skipped that should not be skipped; what needs to be included in the exception list)

If you need to find a lawyer: contact the All China Lawyers Association or your local lawyers association for referral services.

Do not cross this gate to produce a final "ready to close" certification until explicit consent is obtained. Status tracking and "what is blocking" reports do not require this gate.

What this skill does not do

Does not obtain consents, does not submit forms, does not draft documents. It tracks that these need to happen.
Does not decide what is blocking - the equity purchase agreement decides. This skill reads the agreement.
Does not close the transaction. It tells you when you can.