$ 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".
Copy the install command and let the AI configure it · recommended for beginners
Please install the "integration-management" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/claude-for-legal/main/corporate-legal/skills/integration-management/SKILL.md 2. Save it as ~/.claude/skills/integration-management/SKILL.md 3. Reload skills and tell me it's ready
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]"
…
Manage matter workspaces — create, list, switch, close, or detach the active matter. Use in multi-client private practice to keep one client's context separate from another, or when a substantive skill needs to know which matter it's working in.
Draft a DMCA takedown notice, triage one you received, or draft a §512(g) counter-notice. Use when asserting copyright through a §512(c)(3) takedown with the fair-use and perjury gates, when an incoming takedown needs triage into comply / counter / engage / ignore options, or when drafting a §512(g)(3) counter-notice with the consent-to-federal-jurisdiction gate.
Search watched registries for community legal skills, showing matches with descriptions and offering to show the full SKILL.md before install. Use when the user says "browse", "search skills", "find a skill for", "what's out there for", or wants to add a new registry to the watchlist.
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
Draft a brief section in house style, consistent with the case theory — every fact cited, every case checked, every argument tied to the theory. Use when the user says "draft the [section]", "write the statement of facts", "argument section on [issue]", or needs a first draft of a brief section.
Brief a case in your preferred format. In drill-me mode, makes the student state the holding first. Use when the user says "brief [case]", "what's the holding in", "case brief", or pastes a case.