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

1. Read/write ~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/integration-tracker.yaml.
2. 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: "[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]"
  required_consent: true        # true = named in PA Required Consents schedule
  pa_deadline: "[YYYY-MM-DD]"   # only for required_consent: true
  status: "[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: ""

Contract entry structure:

- id: "C-001"
  name: "[contract name or filename]"
  counterparty: "[party name]"
  contract_type: "[MSA / SaaS / lease / IP-license / employment / NDA / other]"
  annual_value: "[amount or unknown]"
  assignment_mechanism: "[auto-assign / consent-required / coc-provision / silent]"
  tier: 1   # 1=Required Consent, 2=material+consent-required, 3=CoC, 4=auto-assign
  required_consent: false
  pa_deadline: "[YYYY-MM-DD or null]"
  status: "[not_reviewed / no_action / consent_pending / outreach_sent / in_negotiation / consent_obtained / assignment_complete / waived / refused / coc_triggered]"
  assigned_to: "[name or null]"
  notes: ""
  last_updated: "[date]"

Mode 1: Initialize

/corporate-legal:integration-management --init [--deal [code]]

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: