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".
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
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".
After any write: show summary of changes and surface any new flags.
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.
Purpose
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.
Tracker file
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.
-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]"required_consent:true# true = named in PA Required Consents schedulepa_deadline:"[YYYY-MM-DD]"# only for required_consent: truestatus:"[not_started / outreach_sent / in_negotiation / obtained / waived / refused]"assigned_to:"[name or null]"outreach_date:"[date or null]"obtained_date:"[date or null]"notes:""
Read ~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/deal-context.md. If not found: ask for deal code name,
target company, close date, deal lead, and outside counsel. Write to
deal-context.md if it doesn't exist.
Read ~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/closing-checklist.yaml if it exists. Any items marked as
post-closing become Day 1 or Day 30 workplan items (inherit status from
closing-checklist).
Step 2: Read deal inputs
A full purchase agreement produces the most complete tracker. The PA's Required
Consents schedule and post-closing covenants section are the authoritative source
for hard deadlines and legal obligations. But the skill can initialize usefully
from whatever is available — partial inputs produce a starter tracker the attorney
fills in rather than an empty page.
What deal artifacts do you have available? Share whatever exists:
Ideal: The purchase agreement (upload or connected document path). I'll read
the post-closing covenants, Required Consents schedule, survival periods, escrow
terms, and earn-out provisions.
Also useful — share any combination of:
Deal summary or term sheet (gives me the key economics and timeline)
Integration to-do list or post-close checklist from outside counsel
Existing workplan or integration tracker (I'll import and continue from it)
Closing checklist — if generated by the M&A cold-start skill, I'll inherit it
automatically from ~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/closing-checklist.yaml
Required Consents list alone (if the PA is held by outside counsel)
If you have nothing written down: Tell me the deal in plain terms — who was
acquired, when it closed, what the main open items are — and I'll build a
starter tracker from the standard Day 1/30/90/180 workplan that you edit.
What changes based on what's provided:
Input
What you get
Full PA
Complete workplan + Required Consents with deadlines + PA dates
PA + contract list
Full tracker + contract assignment tier list
Deal summary / to-do list
Standard workplan skeleton, Required Consents as placeholders
Nothing
Standard workplan scaffold; attorney fills in consents and contract lists
The tracker is designed to be built out progressively — a skeleton today, filled
in as more information becomes available.
From the PA extract:
Required Consents schedule:
For each consent: counterparty name, contract type, and the contractual
deadline. Set as required_consent: true with pa_deadline populated.
Post-closing obligations:
Map each obligation to a workplan item. Assign to the correct phase based
on the deadline. Tag as pa-obligation in deadline_basis.
Key dates:
Required Consents deadline — extract from the PA
Rep and warranty survival expiry — pull the specific survival periods from the PA.
General, fundamental, and tax reps typically have different survival periods; pull
each one the PA defines and record them separately. Do not assume a default.
Escrow release date(s) — extract from the PA
Any earn-out measurement and payment dates — add to pa_dates.earnout_milestones,
owner always set to "finance"
Step 3: Build the phased workplan
Generate standard workplan items for each phase. Add PA obligations extracted
in Step 2. Items inherited from the closing checklist are pre-populated.
Day 1 — legal-owns:
Entity name change filing (if acquired entity is being renamed) [priority: critical]
Bank account signatory updates — notify bank with closing documentation [priority: critical]
Registered agent notification of ownership change [priority: high]
Key IP assignment execution — if any IP assignments were deferred from closing [priority: critical]
Domain name and social media account transfer [priority: high]
D&O insurance — confirm tail policy is bound for acquired entity directors [priority: critical]
Secretary of State ownership notifications where required by state law [priority: high]
Day 1 — legal-supports:
Employee announcement and communications (HR owns, legal reviews) [priority: critical]
Benefits day-1 coverage confirmation (HR owns, legal advises on COBRA and plan terms)
Customer communication letters (business owns, legal reviews for accuracy)
Tier 3 change of control contract resolution [priority: critical]
Day 90 — legal-supports:
Full HR harmonization documentation (HR owns, legal advises on employment law)
Day 180 — legal-owns:
Entity merger filing — if rationalization decision is to merge [priority: high]
Entity dissolution filing — if rationalization decision is to wind down [priority: high]
Full contract novation — contracts requiring acquiror's name [priority: high]
Rep survival tracking — note upcoming expiry date [priority: medium]
Show summary after generating:
Integration tracker initialized — [Deal code] / [Target]
Close date: [date]
Required Consents deadline: [date] ([N] days from today)
Rep survival expires: [date]
Workplan items: [N] ([N] legal-owns, [N] legal-supports)
Required Consents: [N] (from PA schedule)
Desired Consents: [N] (from diligence — no PA deadline)
Contract assignment: not yet imported — run --contracts to populate
Next step: run /corporate-legal:integration-management --contracts to import the
contract list, then --report to see your first status summary.
This is the dedicated contract assignment initialization. Separate from the
main init so it can be run independently and re-run when the contract list
changes.
Step 1: Get the contract list
Two paths — use whichever applies:
Path A: Connected repository
Is your contract repository connected? (Google Drive, Box, SharePoint,
or a VDR that's still accessible post-close?)
If yes: give me the folder path or folder name for the acquired company's
contracts. I'll pull a list of what's there and read each contract for the
assignment clause and counterparty.
Search the connected repository. For each document found:
Extract filename and file path
Read the document — identify: contract party (counterparty name), contract
type (from header or subject matter), assignment clause text, change of
control clause text if present, and annual value if stated.
Path B: Manual list upload
Upload a contract list. This can be:
The Material Contracts schedule from the PA disclosure schedules
A CSV or Excel export from their contract management system
Read the uploaded list. For contracts where no assignment clause text is
provided, set assignment_mechanism to "not_reviewed" and flag for follow-up.
Path C: Disclosure schedule
If neither repository nor list is available, read the Material Contracts
schedule from the PA disclosure schedules (from the PA uploaded in --init).
This gives the minimum required list — parties and contract types. Assignment
clauses will need manual review.
Step 2: Determine assignment mechanism
For each contract, classify the assignment mechanism:
Mechanism
Definition
Tier
consent-required
Explicit clause prohibiting assignment without counterparty consent
1 or 2
coc-provision
Change of control clause giving counterparty termination or consent right triggered by the deal
3
auto-assign
No restriction, or explicit permission to assign to affiliates or successors
4
silent
No assignment clause — default to governing law. Research the governing-law default for contract assignment when the contract is silent and cite the controlling rule. Flag for attorney review.
2
not_reviewed
Could not read or locate assignment clause
Flag for manual review
For contracts flagged in the Required Consents PA schedule: override tier to 1
regardless of assignment mechanism classification.
Step 3: Tier assignment
Tier 1 — Required Consents: [N] contracts
Named in PA schedule, hard deadline [date], must obtain consent
Tier 2 — Material, consent required: [N] contracts
Assignment restriction present, not in PA schedule
Recommended timeline: obtain within Day 90
Tier 3 — Change of control provisions: [N] contracts ⚠️
Counterparty has termination or consent right triggered by close
ACTION REQUIRED: contact counterparty immediately — CoC may already be triggered
Tier 4 — Auto-assign / no action: [N] contracts
Assigns automatically or by affiliate/successor provision
Tracking only — no outreach needed
Not reviewed: [N] contracts
Could not determine assignment mechanism — manual review required
Show tier 3 separately and prominently. A change of control clause may have
already triggered on the close date — counterparty may have a right to terminate
that is running right now.
Step 4: Generate status entries
For each contract, create a tracker entry with:
All extracted fields (counterparty, type, value, mechanism, tier)
[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 post-closing integration records. It inherits their privilege and confidentiality status — distribution beyond the privilege circle can waive privilege. Confirm the recipient list before sending.
INTEGRATION STATUS — [Deal code] / [Target]
[Date] — Day [N] post-close
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
EXECUTIVE SUMMARY
[2-3 sentence paragraph: overall status, biggest risk, key win since last report]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
REQUIRED CONSENTS [deadline: DATE — N days remaining]
Obtained: [N] of [total] ████████░░ [%]
In negotiation: [N]
Outreach sent: [N]
Not started: [N]
Refused: [N] ⚠️
⚠️ AT RISK: [counterparty] — deadline in [N] days, no response to outreach
⚠️ REFUSED: [counterparty] — PA obligation not met; escalate to outside counsel
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CONTRACT ASSIGNMENT
Tier 1 (Required Consents): [N] complete / [N] in progress / [N] pending
Tier 2 (Material contracts): [N] complete / [N] in progress / [N] pending
Tier 3 (CoC provisions): [N] resolved / [N] outstanding ⚠️
Tier 4 (Auto-assign): [N] — no action required
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
WORKPLAN — LEGAL OWNS
🔴 OVERDUE ([N]):
[item] — was due [date]
⏰ DUE THIS WEEK ([N]):
[item] — due [date]
✅ COMPLETED SINCE LAST REPORT ([N]):
[item] — completed [date]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
BLOCKERS & DECISIONS NEEDED
[item] — blocked on: [description] — owner: [name]
[item] — decision needed: [description] — recommend: [option]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
KEY DATES COMING UP
[date] — [milestone / deadline]
[date] — Rep survival expires — confirm no pending indemnification claims
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Manual update: Attorney tells Claude what changed.
"We got the Salesforce consent. Mark it obtained, assigned to [name], date today."
"The entity rationalization decision is to merge. Update status and add the merger
filing to Day 180."
"[Counterparty] refused consent. Flag it and note we need outside counsel on
whether this triggers a PA indemnification claim."
Claude updates the relevant tracker entry, recalculates any downstream status
(e.g., if all tier 1 consents are now obtained, flag the PA obligation as met),
and shows what changed.
Upload update: Workstream owner or outside counsel sends a status document.
Upload the status update from [outside counsel / HR lead / corp dev team].
I'll parse it and update the tracker.
Read the uploaded document. Match described items to tracker entries by
counterparty name or workplan item description. Update status fields.
Flag any items in the update that don't match an existing tracker entry —
may be new items to add.
After any update, show:
Updated [N] items.
Changes:
CON-003 Salesforce: not_started → obtained
W-014 Entity rationalization: in_progress → complete
New flags:
CON-007 [Counterparty]: refused — PA obligation may be unmet. Consider:
outside counsel review of indemnification claim. ⚠️
Export is the shareable format — suitable for outside counsel, corp dev, or a
board integration update.
What this skill does not do
It does not manage business integration workstreams (IT, HR, finance, real
estate). It tracks legal's touchpoints in those workstreams and flags when
legal input is needed. Ownership stays with the business function.
It does not draft the consent request letters or novation agreements — those
are produced by the written-consent skill or by outside counsel.
It does not advise on indemnification claims or PA breach. When a consent is
refused or a deadline is missed, it flags the situation — the legal analysis
of consequences is the attorney's call.
It does not track earn-out performance. Earn-out milestones and payment dates
appear in the tracker as reference dates with owner set to finance. The
business drives the numbers.
It does not read contracts in real time during status reporting. Contract
status is what the attorney has updated in the tracker. The skill reads the
tracker, not the contracts, at report time.
Formula injection defense
Before writing any cell in Excel, Sheets, or CSV output, neutralize formula injection. Counterparty-sourced text (contract quotes, party names, registered agent data, CLM exports) is attacker-controlled. A cell starting with =, +, -, @, , , or will be interpreted as a formula or break the row structure.
Prefix with a single quote:'=SUM(A1:A10) → =SUM(A1:A10) (displayed as text, not executed)
Applies to every cell that contains text sourced from a document, a tool result, or a user paste. Column headers you control and computed values you produce are safe.
