$ loading_
Post-closing M&A integration tracker — phased workplan, consent tracking, contract assignment at scale, weekly status reports. Initializes from whatever deal artifacts are available (purchase agreement, deal summary, closing checklist) and connects to deal-context.md and closing-checklist.yaml from the M&A cold-start. Use when user says "integration", "post-close", "post-closing", "consents outstanding", "contract assignment", "integration status", or "what's left on the deal".
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "integration-management" 技能： 1. 下载 https://raw.githubusercontent.com/anthropics/claude-for-legal/main/corporate-legal/skills/integration-management/SKILL.md 2. 保存为 ~/.claude/skills/integration-management/SKILL.md 3. 装好后重载技能，告诉我可以用了
deal-context.md for deal code, target, close date, deal lead.integration-tracker.yaml if it exists (or create on --init).--init: Mode 1 — read PA, build phased workplan, consent tracker--contracts: Mode 2 — import contract list (repository or upload), tier and classify--report: Mode 3 — generate status report--update: Mode 4 — manual update or parse uploaded status document--export: Mode 5 — CSV or table export~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/integration-tracker.yaml.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.
Outside counsel closes the deal. Legal inherits the mess. This skill is the program management layer for post-closing integration — not the business integration, not IT systems, not HR org design. The legal workstream: consents, contract assignments, entity rationalization, IP recordals, PA obligations. It tracks what's done, what's due, what's blocked, and what needs a decision.
Lives at ~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/integration-tracker.yaml. Read deal-context.md for
the deal code, target name, close date, and deal lead. Inherit any post-close
items from closing-checklist.yaml if it exists.
# integration-tracker.yaml
metadata:
deal_code: "[code]"
target: "[company name]"
close_date: "[YYYY-MM-DD]"
deal_lead: "[name]"
outside_counsel: "[firm and lead attorney]"
last_updated: "[date]"
last_status_report: "[date or null]"
pa_dates:
required_consents_deadline: "[YYYY-MM-DD — extract from PA]"
rep_survival_expires: "[YYYY-MM-DD]"
escrow_release: "[YYYY-MM-DD or null]"
earnout_milestones:
- description: "[milestone]"
measurement_date: "[YYYY-MM-DD]"
payment_date: "[YYYY-MM-DD]"
owner: "finance" # always finance — legal tracks date only
workplan:
day_1:
target_date: "[close_date + 7 days]"
items: []
day_30:
target_date: "[close_date + 30 days]"
items: []
day_90:
target_date: "[close_date + 90 days]"
items: []
day_180:
target_date: "[close_date + 180 days]"
items: []
required_consents: []
desired_consents: []
contracts:
source: "[repository / manual-upload / disclosure-schedule]"
repository_path: "[path or null]"
last_imported: "[date]"
total: 0
tier_1: []
tier_2: []
tier_3: []
tier_4: []
Workplan item structure:
- id: "W-001"
description: "[action item]"
phase: "[day_1 / day_30 / day_90 / day_180]"
owner: "[legal-owns / legal-supports]"
workstream: "[legal / hr / it / finance / real-estate / other]"
priority: "[critical / high / medium / low]"
deadline: "[YYYY-MM-DD or null]"
deadline_basis: "[pa-obligation / regulatory / best-practice]"
status: "[not_started / in_progress / complete / blocked / deferred]"
blocker: "[description or null]"
depends_on: "[item id or null]"
notes: ""
Consent entry structure:
- id: "CON-001"
counterparty: "[name]"
contract_type: "[customer / vendor / lease / IP-license / financial / other]"
…
Review and approve (or reject) pending playbook update proposals from the playbook-monitor agent and apply approved changes to the practice profile. Use when the playbook-monitor agent has surfaced proposals, when the user says "review playbook proposals", "what playbook updates are pending", or wants to step through deviation-driven playbook changes.
Reference: review of SaaS subscription agreements with attention to the terms that matter most in subscription deals — auto-renewal mechanics, price escalation, data portability, uptime SLAs, and subprocessor rights. Loaded by /commercial-legal:review when a SaaS or subscription agreement is detected.
Drafts board or committee meeting minutes in your house format. Auto-detects upcoming board and committee meetings from your calendar, asks for the agenda and any slides or pre-read materials, and produces a complete draft in the format learned from your seed minutes. Also handles written consents in lieu of meetings. Trigger: "board minutes", "draft minutes", "upcoming board meeting", "committee minutes", "written consent", or calendar detection of an upcoming board or committee event.
Aggregate diligence findings into a deal team briefing at the right altitude for the audience — exec summary for leadership, working summary for the team. Use when user says "brief the deal team", "what's the state of diligence", "summarize findings for [audience]", "deal update", or on the briefing cadence.
Entity compliance tracker — initialize, report upcoming deadlines, update status, run health audit, export to CSV. Maintains a compliance-tracker.yaml built from the entity table, calculates filing deadlines by entity and jurisdiction, and surfaces what's due in the next 30/60/90 days. Use when user says "entity compliance", "filing deadlines", "annual reports due", "entity tracker", "what filings are due", "entity health", or "good standing".
Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause. Use when the user says "what changed in this contract over time", "show me the amendment history", "where's the latest [clause]", "how has [provision] evolved", or uploads multiple versions of an agreement.