integration-management

/integration-management

1. Load deal-context.md for deal code, target, close date, deal lead.
2. Load integration-tracker.yaml if it exists (or create on --init).
3. Use the workflow below.
4. Route by flag:
   • --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
5. Read/write ~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/integration-tracker.yaml.
6. 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.

# integration-tracker.yaml
 
metadata:
  deal_code: "[code]"
  target: "[company name]"
  close_date: "[YYYY-MM-DD]"
  deal_lead

Workplan item structure:

Consent entry structure:

Contract entry structure:

Mode 1: Initialize

Step 1: Load deal context

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:

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)

Day 30 — legal-owns:

• Required Consents initial push — contact all counterparties, document outreach [priority: critical]
• IP assignment recordal at USPTO (patents, trademarks) [priority: high]
• Copyright assignment filing [priority: medium]
• Trademark assignment recording [priority: high]
• Material contract review — complete tier 1 and tier 2 contract assignment analysis [priority: high]
• Insurance tail policy final confirmation [priority: high]

Day 30 — legal-supports:

• Data migration privacy review (IT owns, legal advises on data transfer mechanisms)
• Real estate lease review for assignment provisions (facilities owns, legal advises)

Day 90 — legal-owns:

• Required Consents deadline — all Required Consents must be obtained or escalated [priority: critical, deadline: pa_dates.required_consents_deadline]
• Entity rationalization decision — recommend keep separate / merge / dissolve [priority: high]
• Benefits plan assumption or termination documentation [priority: high]
• Secondary consent push — remaining outstanding consents [priority: high]
• 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:

Mode 2: Contract Assignment

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
• A manually prepared list

Minimum required columns: Contract Name, Counterparty. Helpful but optional: Contract Type, Annual Value, Assignment Clause text.

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:

For contracts flagged in the Required Consents PA schedule: override tier to 1 regardless of assignment mechanism classification.

Step 3: Tier assignment

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)
• Initial status: tier 4 → no_action; tier 3 → coc_triggered; tiers 1/2 → consent_pending; not_reviewed → not_reviewed
• pa_deadline populated for tier 1 from Required Consents schedule

Mode 3: Status Report

Reads current tracker state. Produces:

Mode 4: Update

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:

Mode 5: Export

Produces a flat CSV or markdown table. Default: all sections, CSV.

CSV format — one row per item, section indicated by a section column. Columns vary by section:

Workplan: id, phase, description, owner, workstream, priority, deadline, status, blocker

Consents: id, counterparty, contract_type, required_consent, pa_deadline, status, assigned_to, obtained_date, notes

Contracts: id, name, counterparty, contract_type, annual_value, assignment_mechanism, tier, required_consent, pa_deadline, status, assigned_to, notes

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.
• CSV: also escape embedded commas, double quotes, newlines (RFC 4180 quoting).
• This is not optional. A spreadsheet your user opens in Excel that triggers a macro or exfiltrates data via DDE is a supply-chain attack on your user.