[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718CVJ9STPGSMC47GTK3HHR":3,"skill-same:01M718CVJ9STPGSMC47GTK3HHR":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M718CVJ9STPGSMC47GTK3HHR","integration-management",null,"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\".","anthropics\u002Fclaude-for-legal","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M7189QY7HXHMC9BW4MFHPZ6H",10006,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fcorporate-legal\u002Fskills\u002Fintegration-management\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"integration management","management","integration","export","start","status","at","update","tracker","close","closing","reports","agreement","code","when","init","cold-start","purchase","cold","weekly","2026-11-10 10:12:30",false,"---\nname: integration-management\ndescription: >\n  Post-closing M&A integration tracker — phased workplan, consent tracking,\n  contract assignment at scale, weekly status reports. Initializes from whatever\n  deal artifacts are available (purchase agreement, deal summary, closing\n  checklist) and connects to deal-context.md and closing-checklist.yaml from the\n  M&A cold-start. Use when user says \"integration\", \"post-close\", \"post-closing\",\n  \"consents outstanding\", \"contract assignment\", \"integration status\", or\n  \"what's left on the deal\".\nargument-hint: \"[--init | --contracts | --report | --update | --export [--format csv|table] [--section all|consents|contracts|workplan]] [--deal [code]]\"\n---\n\n# \u002Fintegration-management\n\n1. Load `deal-context.md` for deal code, target, close date, deal lead.\n2. Load `integration-tracker.yaml` if it exists (or create on --init).\n3. Use the workflow below.\n4. Route by flag:\n   - `--init`: Mode 1 — read PA, build phased workplan, consent tracker\n   - `--contracts`: Mode 2 — import contract list (repository or upload), tier and classify\n   - `--report`: Mode 3 — generate status report\n   - `--update`: Mode 4 — manual update or parse uploaded status document\n   - `--export`: Mode 5 — CSV or table export\n5. Read\u002Fwrite `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fdeals\u002F[code]\u002Fintegration-tracker.yaml`.\n6. After any write: show summary of changes and surface any new flags.\n\n---\n\n## Matter context\n\n**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 `\u002Fcorporate-legal:matter-workspace switch \u003Cslug>` or say `practice-level`.\" Load the active matter's `matter.md` for matter-specific context and overrides. Write outputs to the matter folder at `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fmatters\u002F\u003Cmatter-slug>\u002F`. Never read another matter's files unless `Cross-matter context` is `on`.\n\n---\n\n## Purpose\n\nOutside counsel closes the deal. Legal inherits the mess. This skill is the\nprogram management layer for post-closing integration — not the business\nintegration, not IT systems, not HR org design. The legal workstream: consents,\ncontract assignments, entity rationalization, IP recordals, PA obligations.\nIt tracks what's done, what's due, what's blocked, and what needs a decision.\n\n---\n\n## Tracker file\n\nLives at `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fdeals\u002F[code]\u002Fintegration-tracker.yaml`. Read `deal-context.md` for\nthe deal code, target name, close date, and deal lead. Inherit any post-close\nitems from `closing-checklist.yaml` if it exists.\n\n```yaml\n# integration-tracker.yaml\n\nmetadata:\n  deal_code: \"[code]\"\n  target: \"[company name]\"\n  close_date: \"[YYYY-MM-DD]\"\n  deal_lead: \"[name]\"\n  outside_counsel: \"[firm and lead attorney]\"\n  last_updated: \"[date]\"\n  last_status_report: \"[date or null]\"\n\npa_dates:\n  required_consents_deadline: \"[YYYY-MM-DD — extract from PA]\"\n  rep_survival_expires: \"[YYYY-MM-DD]\"\n  escrow_release: \"[YYYY-MM-DD or null]\"\n  earnout_milestones:\n    - description: \"[milestone]\"\n      measurement_date: \"[YYYY-MM-DD]\"\n      payment_date: \"[YYYY-MM-DD]\"\n      owner: \"finance\"   # always finance — legal tracks date only\n\nworkplan:\n  day_1:\n    target_date: \"[close_date + 7 days]\"\n    items: []\n  day_30:\n    target_date: \"[close_date + 30 days]\"\n    items: []\n  day_90:\n    target_date: \"[close_date + 90 days]\"\n    items: []\n  day_180:\n    target_date: \"[close_date + 180 days]\"\n    items: []\n\nrequired_consents: []\ndesired_consents: []\n\ncontracts:\n  source: \"[repository \u002F manual-upload \u002F disclosure-schedule]\"\n  repository_path: \"[path or null]\"\n  last_imported: \"[date]\"\n  total: 0\n  tier_1: []\n  tier_2: []\n  tier_3: []\n  tier_4: []\n```\n\n**Workplan item structure:**\n```yaml\n- id: \"W-001\"\n  description: \"[action item]\"\n  phase: \"[day_1 \u002F day_30 \u002F day_90 \u002F day_180]\"\n  owner: \"[legal-owns \u002F legal-supports]\"\n  workstream: \"[legal \u002F hr \u002F it \u002F finance \u002F real-estate \u002F other]\"\n  priority: \"[critical \u002F high \u002F medium \u002F low]\"\n  deadline: \"[YYYY-MM-DD or null]\"\n  deadline_basis: \"[pa-obligation \u002F regulatory \u002F best-practice]\"\n  status: \"[not_started \u002F in_progress \u002F complete \u002F blocked \u002F deferred]\"\n  blocker: \"[description or null]\"\n  depends_on: \"[item id or null]\"\n  notes: \"\"\n```\n\n**Consent entry structure:**\n```yaml\n- id: \"CON-001\"\n  counterparty: \"[name]\"\n  contract_type: \"[customer \u002F vendor \u002F lease \u002F IP-license \u002F financial \u002F other]\"\n  required_consent: true        # true = named in PA Required Consents schedule\n  pa_deadline: \"[YYYY-MM-DD]\"   # only for required_consent: true\n  status: \"[not_started \u002F outreach_sent \u002F in_negotiation \u002F obtained \u002F waived \u002F refused]\"\n  assigned_to: \"[name or null]\"\n  outreach_date: \"[date or null]\"\n  obtained_date: \"[date or null]\"\n  notes: \"\"\n```\n\n**Contract entry structure:**\n```yaml\n- id: \"C-001\"\n  name: \"[contract name or filename]\"\n  counterparty: \"[party name]\"\n  contract_type: \"[MSA \u002F SaaS \u002F lease \u002F IP-license \u002F employment \u002F NDA \u002F other]\"\n  annual_value: \"[amount or unknown]\"\n  assignment_mechanism: \"[auto-assign \u002F consent-required \u002F coc-provision \u002F silent]\"\n  tier: 1   # 1=Required Consent, 2=material+consent-required, 3=CoC, 4=auto-assign\n  required_consent: false\n  pa_deadline: \"[YYYY-MM-DD or null]\"\n  status: \"[not_reviewed \u002F no_action \u002F consent_pending \u002F outreach_sent \u002F in_negotiation \u002F consent_obtained \u002F assignment_complete \u002F waived \u002F refused \u002F coc_triggered]\"\n  assigned_to: \"[name or null]\"\n  notes: \"\"\n  last_updated: \"[date]\"\n```\n\n---\n\n## Mode 1: Initialize\n\n```\n\u002Fcorporate-legal:integration-management --init [--deal [code]]\n```\n\n### Step 1: Load deal context\n\nRead `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fdeals\u002F[code]\u002Fdeal-context.md`. If not found: ask for deal code name,\ntarget company, close date, deal lead, and outside counsel. Write to\ndeal-context.md if it doesn't exist.\n\nRead `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fdeals\u002F[code]\u002Fclosing-checklist.yaml` if it exists. Any items marked as\npost-closing become Day 1 or Day 30 workplan items (inherit status from\nclosing-checklist).\n\n### Step 2: Read deal inputs\n\n**A full purchase agreement produces the most complete tracker.** The PA's Required\nConsents schedule and post-closing covenants section are the authoritative source\nfor hard deadlines and legal obligations. But the skill can initialize usefully\nfrom whatever is available — partial inputs produce a starter tracker the attorney\nfills in rather than an empty page.\n\n> What deal artifacts do you have available? Share whatever exists:\n>\n> **Ideal:** The purchase agreement (upload or connected document path). I'll read\n> the post-closing covenants, Required Consents schedule, survival periods, escrow\n> terms, and earn-out provisions.\n>\n> **Also useful — share any combination of:**\n> - Deal summary or term sheet (gives me the key economics and timeline)\n> - Integration to-do list or post-close checklist from outside counsel\n> - Existing workplan or integration tracker (I'll import and continue from it)\n> - Closing checklist — if generated by the M&A cold-start skill, I'll inherit it\n>   automatically from `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fdeals\u002F[code]\u002Fclosing-checklist.yaml`\n> - Required Consents list alone (if the PA is held by outside counsel)\n>\n> **If you have nothing written down:** Tell me the deal in plain terms — who was\n> acquired, when it closed, what the main open items are — and I'll build a\n> starter tracker from the standard Day 1\u002F30\u002F90\u002F180 workplan that you edit.\n\n**What changes based on what's provided:**\n\n| Input | What you get |\n|---|---|\n| Full PA | Complete workplan + Required Consents with deadlines + PA dates |\n| PA + contract list | Full tracker + contract assignment tier list |\n| Deal summary \u002F to-do list | Standard workplan skeleton, Required Consents as placeholders |\n| Nothing | Standard workplan scaffold; attorney fills in consents and contract lists |\n\nThe tracker is designed to be built out progressively — a skeleton today, filled\nin as more information becomes available.\n\n**From the PA extract:**\n\n*Required Consents schedule:*\n- For each consent: counterparty name, contract type, and the contractual\n  deadline. Set as required_consent: true with pa_deadline populated.\n\n*Post-closing obligations:*\n- Map each obligation to a workplan item. Assign to the correct phase based\n  on the deadline. Tag as pa-obligation in deadline_basis.\n\n*Key dates:*\n- Required Consents deadline — extract from the PA\n- Rep and warranty survival expiry — pull the specific survival periods from the PA.\n  General, fundamental, and tax reps typically have different survival periods; pull\n  each one the PA defines and record them separately. Do not assume a default.\n- Escrow release date(s) — extract from the PA\n- Any earn-out measurement and payment dates — add to pa_dates.earnout_milestones,\n  owner always set to \"finance\"\n\n### Step 3: Build the phased workplan\n\nGenerate standard workplan items for each phase. Add PA obligations extracted\nin Step 2. Items inherited from the closing checklist are pre-populated.\n\n**Day 1 — legal-owns:**\n- Entity name change filing (if acquired entity is being renamed) [priority: critical]\n- Bank account signatory updates — notify bank with closing documentation [priority: critical]\n- Registered agent notification of ownership change [priority: high]\n- Key IP assignment execution — if any IP assignments were deferred from closing [priority: critical]\n- Domain name and social media account transfer [priority: high]\n- D&O insurance — confirm tail policy is bound for acquired entity directors [priority: critical]\n- Secretary of State ownership notifications where required by state law [priority: high]\n\n**Day 1 — legal-supports:**\n- Employee announcement and communications (HR owns, legal reviews) [priority: critical]\n- Benefits day-1 coverage confirmation (HR owns, legal advises on COBRA and plan terms)\n- Customer communication letters (business owns, legal reviews for accuracy)\n\n**Day 30 — legal-owns:**\n- Required Consents initial push — contact all counterparties, document outreach [priority: critical]\n- IP assignment recordal at USPTO (patents, trademarks) [priority: high]\n- Copyright assignment filing [priority: medium]\n- Trademark assignment recording [priority: high]\n- Material contract review — complete tier 1 and tier 2 contract assignment analysis [priority: high]\n- Insurance tail policy final confirmation [priority: high]\n\n**Day 30 — legal-supports:**\n- Data migration privacy review (IT owns, legal advises on data transfer mechanisms)\n- Real estate lease review for assignment provisions (facilities owns, legal advises)\n\n**Day 90 — legal-owns:**\n- Required Consents deadline — all Required Consents must be obtained or escalated [priority: critical, deadline: pa_dates.required_consents_deadline]\n- Entity rationalization decision — recommend keep separate \u002F merge \u002F dissolve [priority: high]\n- Benefits plan assumption or termination documentation [priority: high]\n- Secondary consent push — remaining outstanding consents [priority: high]\n- Tier 3 change of control contract resolution [priority: critical]\n\n**Day 90 — legal-supports:**\n- Full HR harmonization documentation (HR owns, legal advises on employment law)\n\n**Day 180 — legal-owns:**\n- Entity merger filing — if rationalization decision is to merge [priority: high]\n- Entity dissolution filing — if rationalization decision is to wind down [priority: high]\n- Full contract novation — contracts requiring acquiror's name [priority: high]\n- Rep survival tracking — note upcoming expiry date [priority: medium]\n\nShow summary after generating:\n\n```\nIntegration tracker initialized — [Deal code] \u002F [Target]\n\nClose date: [date]\nRequired Consents deadline: [date] ([N] days from today)\nRep survival expires: [date]\n\nWorkplan items: [N] ([N] legal-owns, [N] legal-supports)\nRequired Consents: [N] (from PA schedule)\nDesired Consents: [N] (from diligence — no PA deadline)\n\nContract assignment: not yet imported — run --contracts to populate\n\nNext step: run \u002Fcorporate-legal:integration-management --contracts to import the\ncontract list, then --report to see your first status summary.\n```\n\n---\n\n## Mode 2: Contract Assignment\n\n```\n\u002Fcorporate-legal:integration-management --contracts [--deal [code]]\n```\n\nThis is the dedicated contract assignment initialization. Separate from the\nmain init so it can be run independently and re-run when the contract list\nchanges.\n\n### Step 1: Get the contract list\n\nTwo paths — use whichever applies:\n\n**Path A: Connected repository**\n\n> Is your contract repository connected? (Google Drive, Box, SharePoint,\n> or a VDR that's still accessible post-close?)\n>\n> If yes: give me the folder path or folder name for the acquired company's\n> contracts. I'll pull a list of what's there and read each contract for the\n> assignment clause and counterparty.\n\nSearch the connected repository. For each document found:\n- Extract filename and file path\n- Read the document — identify: contract party (counterparty name), contract\n  type (from header or subject matter), assignment clause text, change of\n  control clause text if present, and annual value if stated.\n\n**Path B: Manual list upload**\n\n> Upload a contract list. This can be:\n> - The Material Contracts schedule from the PA disclosure schedules\n> - A CSV or Excel export from their contract management system\n> - A manually prepared list\n>\n> Minimum required columns: Contract Name, Counterparty. Helpful but optional:\n> Contract Type, Annual Value, Assignment Clause text.\n\nRead the uploaded list. For contracts where no assignment clause text is\nprovided, set assignment_mechanism to \"not_reviewed\" and flag for follow-up.\n\n**Path C: Disclosure schedule**\n\nIf neither repository nor list is available, read the Material Contracts\nschedule from the PA disclosure schedules (from the PA uploaded in --init).\nThis gives the minimum required list — parties and contract types. Assignment\nclauses will need manual review.\n\n### Step 2: Determine assignment mechanism\n\nFor each contract, classify the assignment mechanism:\n\n| Mechanism | Definition | Tier |\n|---|---|---|\n| `consent-required` | Explicit clause prohibiting assignment without counterparty consent | 1 or 2 |\n| `coc-provision` | Change of control clause giving counterparty termination or consent right triggered by the deal | 3 |\n| `auto-assign` | No restriction, or explicit permission to assign to affiliates or successors | 4 |\n| `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 |\n| `not_reviewed` | Could not read or locate assignment clause | Flag for manual review |\n\nFor contracts flagged in the Required Consents PA schedule: override tier to 1\nregardless of assignment mechanism classification.\n\n### Step 3: Tier assignment\n\n```\nTier 1 — Required Consents: [N] contracts\n  Named in PA schedule, hard deadline [date], must obtain consent\n\nTier 2 — Material, consent required: [N] contracts\n  Assignment restriction present, not in PA schedule\n  Recommended timeline: obtain within Day 90\n\nTier 3 — Change of control provisions: [N] contracts ⚠️\n  Counterparty has termination or consent right triggered by close\n  ACTION REQUIRED: contact counterparty immediately — CoC may already be triggered\n\nTier 4 — Auto-assign \u002F no action: [N] contracts\n  Assigns automatically or by affiliate\u002Fsuccessor provision\n  Tracking only — no outreach needed\n\nNot reviewed: [N] contracts\n  Could not determine assignment mechanism — manual review required\n```\n\nShow tier 3 separately and prominently. A change of control clause may have\nalready triggered on the close date — counterparty may have a right to terminate\nthat is running right now.\n\n### Step 4: Generate status entries\n\nFor each contract, create a tracker entry with:\n- All extracted fields (counterparty, type, value, mechanism, tier)\n- Initial status: tier 4 → `no_action`; tier 3 → `coc_triggered`; tiers 1\u002F2 → `consent_pending`; not_reviewed → `not_reviewed`\n- pa_deadline populated for tier 1 from Required Consents schedule\n\n---\n\n## Mode 3: Status Report\n\n```\n\u002Fcorporate-legal:integration-management --report [--deal [code]]\n```\n\nReads current tracker state. Produces:\n\n```\n[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]\n\n> 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.\n\nINTEGRATION STATUS — [Deal code] \u002F [Target]\n[Date] — Day [N] post-close\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nEXECUTIVE SUMMARY\n[2-3 sentence paragraph: overall status, biggest risk, key win since last report]\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nREQUIRED CONSENTS  [deadline: DATE — N days remaining]\n  Obtained:        [N] of [total]  ████████░░  [%]\n  In negotiation:  [N]\n  Outreach sent:   [N]\n  Not started:     [N]\n  Refused:         [N] ⚠️\n\n⚠️ AT RISK: [counterparty] — deadline in [N] days, no response to outreach\n⚠️ REFUSED: [counterparty] — PA obligation not met; escalate to outside counsel\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nCONTRACT ASSIGNMENT\n  Tier 1 (Required Consents):   [N] complete \u002F [N] in progress \u002F [N] pending\n  Tier 2 (Material contracts):  [N] complete \u002F [N] in progress \u002F [N] pending\n  Tier 3 (CoC provisions):      [N] resolved \u002F [N] outstanding ⚠️\n  Tier 4 (Auto-assign):         [N] — no action required\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nWORKPLAN — LEGAL OWNS\n  🔴 OVERDUE ([N]):\n    [item] — was due [date]\n\n  ⏰ DUE THIS WEEK ([N]):\n    [item] — due [date]\n\n  ✅ COMPLETED SINCE LAST REPORT ([N]):\n    [item] — completed [date]\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nBLOCKERS & DECISIONS NEEDED\n  [item] — blocked on: [description] — owner: [name]\n  [item] — decision needed: [description] — recommend: [option]\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nKEY DATES COMING UP\n  [date] — [milestone \u002F deadline]\n  [date] — Rep survival expires — confirm no pending indemnification claims\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n```\n\n---\n\n## Mode 4: Update\n\n```\n\u002Fcorporate-legal:integration-management --update [--deal [code]]\n```\n\n**Manual update:** Attorney tells Claude what changed.\n\n> \"We got the Salesforce consent. Mark it obtained, assigned to [name], date today.\"\n> \"The entity rationalization decision is to merge. Update status and add the merger\n> filing to Day 180.\"\n> \"[Counterparty] refused consent. Flag it and note we need outside counsel on\n> whether this triggers a PA indemnification claim.\"\n\nClaude updates the relevant tracker entry, recalculates any downstream status\n(e.g., if all tier 1 consents are now obtained, flag the PA obligation as met),\nand shows what changed.\n\n**Upload update:** Workstream owner or outside counsel sends a status document.\n\n> Upload the status update from [outside counsel \u002F HR lead \u002F corp dev team].\n> I'll parse it and update the tracker.\n\nRead the uploaded document. Match described items to tracker entries by\ncounterparty name or workplan item description. Update status fields.\nFlag any items in the update that don't match an existing tracker entry —\nmay be new items to add.\n\nAfter any update, show:\n```\nUpdated [N] items.\n\nChanges:\n  CON-003 Salesforce: not_started → obtained\n  W-014 Entity rationalization: in_progress → complete\n\nNew flags:\n  CON-007 [Counterparty]: refused — PA obligation may be unmet. Consider:\n  outside counsel review of indemnification claim. ⚠️\n```\n\n---\n\n## Mode 5: Export\n\n```\n\u002Fcorporate-legal:integration-management --export [--format csv|table] [--section all|consents|contracts|workplan]\n```\n\nProduces a flat CSV or markdown table. Default: all sections, CSV.\n\nCSV format — one row per item, section indicated by a `section` column.\nColumns vary by section:\n\n*Workplan:* id, phase, description, owner, workstream, priority, deadline, status, blocker\n\n*Consents:* id, counterparty, contract_type, required_consent, pa_deadline, status, assigned_to, obtained_date, notes\n\n*Contracts:* id, name, counterparty, contract_type, annual_value, assignment_mechanism, tier, required_consent, pa_deadline, status, assigned_to, notes\n\nExport is the shareable format — suitable for outside counsel, corp dev, or a\nboard integration update.\n\n---\n\n## What this skill does not do\n\n- It does not manage business integration workstreams (IT, HR, finance, real\n  estate). It tracks legal's touchpoints in those workstreams and flags when\n  legal input is needed. Ownership stays with the business function.\n- It does not draft the consent request letters or novation agreements — those\n  are produced by the written-consent skill or by outside counsel.\n- It does not advise on indemnification claims or PA breach. When a consent is\n  refused or a deadline is missed, it flags the situation — the legal analysis\n  of consequences is the attorney's call.\n- It does not track earn-out performance. Earn-out milestones and payment dates\n  appear in the tracker as reference dates with owner set to finance. The\n  business drives the numbers.\n- It does not read contracts in real time during status reporting. Contract\n  status is what the attorney has updated in the tracker. The skill reads the\n  tracker, not the contracts, at report time.\n\n\n## Formula injection defense\n\nBefore 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 `=`, `+`, `-`, `@`, `\t`, `\n`, or `\n` will be interpreted as a formula or break the row structure.\n\n- **Prefix with a single quote:** `'=SUM(A1:A10)` → `=SUM(A1:A10)` (displayed as text, not executed)\n- **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.\n- **CSV: also escape embedded commas, double quotes, newlines** (RFC 4180 quoting).\n- 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.\n","# \u002Fintegration-management\n\n1. Load `deal-context.md` for deal code, target, close date, deal lead.\n2. Load `integration-tracker.yaml` if it exists (or create on --init).\n3. Use the workflow below.\n4. Route by flag:\n   - `--init`: Mode 1 — read PA, build phased workplan, consent tracker\n   - `--contracts`: Mode 2 — import contract list (repository or upload), tier and classify\n   - `--report`: Mode 3 — generate status report\n   - `--update`: Mode 4 — manual update or parse uploaded status document\n   - `--export`: Mode 5 — CSV or table export\n5. Read\u002Fwrite `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fdeals\u002F[code]\u002Fintegration-tracker.yaml`.\n6. After any write: show summary of changes and surface any new flags.\n\n---\n\n## Matter context\n\n**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 `\u002Fcorporate-legal:matter-workspace switch \u003Cslug>` or say `practice-level`.\" Load the active matter's `matter.md` for matter-specific context and overrides. Write outputs to the matter folder at `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fmatters\u002F\u003Cmatter-slug>\u002F`. Never read another matter's files unless `Cross-matter context` is `on`.\n\n---\n\n## Purpose\n\nOutside counsel closes the deal. Legal inherits the mess. This skill is the\nprogram management layer for post-closing integration — not the business\nintegration, not IT systems, not HR org design. The legal workstream: consents,\ncontract assignments, entity rationalization, IP recordals, PA obligations.\nIt tracks what's done, what's due, what's blocked, and what needs a decision.\n\n---\n\n## Tracker file\n\nLives at `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fdeals\u002F[code]\u002Fintegration-tracker.yaml`. Read `deal-context.md` for\nthe deal code, target name, close date, and deal lead. Inherit any post-close\nitems from `closing-checklist.yaml` if it exists.\n\n```yaml\n# integration-tracker.yaml\n\nmetadata:\n  deal_code: \"[code]\"\n  target: \"[company name]\"\n  close_date: \"[YYYY-MM-DD]\"\n  deal_lead: \"[name]\"\n  outside_counsel: \"[firm and lead attorney]\"\n  last_updated: \"[date]\"\n  last_status_report: \"[date or null]\"\n\npa_dates:\n  required_consents_deadline: \"[YYYY-MM-DD — extract from PA]\"\n  rep_survival_expires: \"[YYYY-MM-DD]\"\n  escrow_release: \"[YYYY-MM-DD or null]\"\n  earnout_milestones:\n    - description: \"[milestone]\"\n      measurement_date: \"[YYYY-MM-DD]\"\n      payment_date: \"[YYYY-MM-DD]\"\n      owner: \"finance\"   # always finance — legal tracks date only\n\nworkplan:\n  day_1:\n    target_date: \"[close_date + 7 days]\"\n    items: []\n  day_30:\n    target_date: \"[close_date + 30 days]\"\n    items: []\n  day_90:\n    target_date: \"[close_date + 90 days]\"\n    items: []\n  day_180:\n    target_date: \"[close_date + 180 days]\"\n    items: []\n\nrequired_consents: []\ndesired_consents: []\n\ncontracts:\n  source: \"[repository \u002F manual-upload \u002F disclosure-schedule]\"\n  repository_path: \"[path or null]\"\n  last_imported: \"[date]\"\n  total: 0\n  tier_1: []\n  tier_2: []\n  tier_3: []\n  tier_4: []\n```\n\n**Workplan item structure:**\n```yaml\n- id: \"W-001\"\n  description: \"[action item]\"\n  phase: \"[day_1 \u002F day_30 \u002F day_90 \u002F day_180]\"\n  owner: \"[legal-owns \u002F legal-supports]\"\n  workstream: \"[legal \u002F hr \u002F it \u002F finance \u002F real-estate \u002F other]\"\n  priority: \"[critical \u002F high \u002F medium \u002F low]\"\n  deadline: \"[YYYY-MM-DD or null]\"\n  deadline_basis: \"[pa-obligation \u002F regulatory \u002F best-practice]\"\n  status: \"[not_started \u002F in_progress \u002F complete \u002F blocked \u002F deferred]\"\n  blocker: \"[description or null]\"\n  depends_on: \"[item id or null]\"\n  notes: \"\"\n```\n\n**Consent entry structure:**\n```yaml\n- id: \"CON-001\"\n  counterparty: \"[name]\"\n  contract_type: \"[customer \u002F vendor \u002F lease \u002F IP-license \u002F financial \u002F other]\"\n  required_consent: true        # true = named in PA Required Consents schedule\n  pa_deadline: \"[YYYY-MM-DD]\"   # only for required_consent: true\n  status: \"[not_started \u002F outreach_sent \u002F in_negotiation \u002F obtained \u002F waived \u002F refused]\"\n  assigned_to: \"[name or null]\"\n  outreach_date: \"[date or null]\"\n  obtained_date: \"[date or null]\"\n  notes: \"\"\n```\n\n**Contract entry structure:**\n```yaml\n- id: \"C-001\"\n  name: \"[contract name or filename]\"\n  counterparty: \"[party name]\"\n  contract_type: \"[MSA \u002F SaaS \u002F lease \u002F IP-license \u002F employment \u002F NDA \u002F other]\"\n  annual_value: \"[amount or unknown]\"\n  assignment_mechanism: \"[auto-assign \u002F consent-required \u002F coc-provision \u002F silent]\"\n  tier: 1   # 1=Required Consent, 2=material+consent-required, 3=CoC, 4=auto-assign\n  required_consent: false\n  pa_deadline: \"[YYYY-MM-DD or null]\"\n  status: \"[not_reviewed \u002F no_action \u002F consent_pending \u002F outreach_sent \u002F in_negotiation \u002F consent_obtained \u002F assignment_complete \u002F waived \u002F refused \u002F coc_triggered]\"\n  assigned_to: \"[name or null]\"\n  notes: \"\"\n  last_updated: \"[date]\"\n```\n\n---\n\n## Mode 1: Initialize\n\n```\n\u002Fcorporate-legal:integration-management --init [--deal [code]]\n```\n\n### Step 1: Load deal context\n\nRead `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fdeals\u002F[code]\u002Fdeal-context.md`. If not found: ask for deal code name,\ntarget company, close date, deal lead, and outside counsel. Write to\ndeal-context.md if it doesn't exist.\n\nRead `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fdeals\u002F[code]\u002Fclosing-checklist.yaml` if it exists. Any items marked as\npost-closing become Day 1 or Day 30 workplan items (inherit status from\nclosing-checklist).\n\n### Step 2: Read deal inputs\n\n**A full purchase agreement produces the most complete tracker.** The PA's Required\nConsents schedule and post-closing covenants section are the authoritative source\nfor hard deadlines and legal obligations. But the skill can initialize usefully\nfrom whatever is available — partial inputs produce a starter tracker the attorney\nfills in rather than an empty page.\n\n> What deal artifacts do you have available? Share whatever exists:\n>\n> **Ideal:** The purchase agreement (upload or connected document path). I'll read\n> the post-closing covenants, Required Consents schedule, survival periods, escrow\n> terms, and earn-out provisions.\n>\n> **Also useful — share any combination of:**\n> - Deal summary or term sheet (gives me the key economics and timeline)\n> - Integration to-do list or post-close checklist from outside counsel\n> - Existing workplan or integration tracker (I'll import and continue from it)\n> - Closing checklist — if generated by the M&A cold-start skill, I'll inherit it\n>   automatically from `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fdeals\u002F[code]\u002Fclosing-checklist.yaml`\n> - Required Consents list alone (if the PA is held by outside counsel)\n>\n> **If you have nothing written down:** Tell me the deal in plain terms — who was\n> acquired, when it closed, what the main open items are — and I'll build a\n> starter tracker from the standard Day 1\u002F30\u002F90\u002F180 workplan that you edit.\n\n**What changes based on what's provided:**\n\n| Input | What you get |\n|---|---|\n| Full PA | Complete workplan + Required Consents with deadlines + PA dates |\n| PA + contract list | Full tracker + contract assignment tier list |\n| Deal summary \u002F to-do list | Standard workplan skeleton, Required Consents as placeholders |\n| Nothing | Standard workplan scaffold; attorney fills in consents and contract lists |\n\nThe tracker is designed to be built out progressively — a skeleton today, filled\nin as more information becomes available.\n\n**From the PA extract:**\n\n*Required Consents schedule:*\n- For each consent: counterparty name, contract type, and the contractual\n  deadline. Set as required_consent: true with pa_deadline populated.\n\n*Post-closing obligations:*\n- Map each obligation to a workplan item. Assign to the correct phase based\n  on the deadline. Tag as pa-obligation in deadline_basis.\n\n*Key dates:*\n- Required Consents deadline — extract from the PA\n- Rep and warranty survival expiry — pull the specific survival periods from the PA.\n  General, fundamental, and tax reps typically have different survival periods; pull\n  each one the PA defines and record them separately. Do not assume a default.\n- Escrow release date(s) — extract from the PA\n- Any earn-out measurement and payment dates — add to pa_dates.earnout_milestones,\n  owner always set to \"finance\"\n\n### Step 3: Build the phased workplan\n\nGenerate standard workplan items for each phase. Add PA obligations extracted\nin Step 2. Items inherited from the closing checklist are pre-populated.\n\n**Day 1 — legal-owns:**\n- Entity name change filing (if acquired entity is being renamed) [priority: critical]\n- Bank account signatory updates — notify bank with closing documentation [priority: critical]\n- Registered agent notification of ownership change [priority: high]\n- Key IP assignment execution — if any IP assignments were deferred from closing [priority: critical]\n- Domain name and social media account transfer [priority: high]\n- D&O insurance — confirm tail policy is bound for acquired entity directors [priority: critical]\n- Secretary of State ownership notifications where required by state law [priority: high]\n\n**Day 1 — legal-supports:**\n- Employee announcement and communications (HR owns, legal reviews) [priority: critical]\n- Benefits day-1 coverage confirmation (HR owns, legal advises on COBRA and plan terms)\n- Customer communication letters (business owns, legal reviews for accuracy)\n\n**Day 30 — legal-owns:**\n- Required Consents initial push — contact all counterparties, document outreach [priority: critical]\n- IP assignment recordal at USPTO (patents, trademarks) [priority: high]\n- Copyright assignment filing [priority: medium]\n- Trademark assignment recording [priority: high]\n- Material contract review — complete tier 1 and tier 2 contract assignment analysis [priority: high]\n- Insurance tail policy final confirmation [priority: high]\n\n**Day 30 — legal-supports:**\n- Data migration privacy review (IT owns, legal advises on data transfer mechanisms)\n- Real estate lease review for assignment provisions (facilities owns, legal advises)\n\n**Day 90 — legal-owns:**\n- Required Consents deadline — all Required Consents must be obtained or escalated [priority: critical, deadline: pa_dates.required_consents_deadline]\n- Entity rationalization decision — recommend keep separate \u002F merge \u002F dissolve [priority: high]\n- Benefits plan assumption or termination documentation [priority: high]\n- Secondary consent push — remaining outstanding consents [priority: high]\n- Tier 3 change of control contract resolution [priority: critical]\n\n**Day 90 — legal-supports:**\n- Full HR harmonization documentation (HR owns, legal advises on employment law)\n\n**Day 180 — legal-owns:**\n- Entity merger filing — if rationalization decision is to merge [priority: high]\n- Entity dissolution filing — if rationalization decision is to wind down [priority: high]\n- Full contract novation — contracts requiring acquiror's name [priority: high]\n- Rep survival tracking — note upcoming expiry date [priority: medium]\n\nShow summary after generating:\n\n```\nIntegration tracker initialized — [Deal code] \u002F [Target]\n\nClose date: [date]\nRequired Consents deadline: [date] ([N] days from today)\nRep survival expires: [date]\n\nWorkplan items: [N] ([N] legal-owns, [N] legal-supports)\nRequired Consents: [N] (from PA schedule)\nDesired Consents: [N] (from diligence — no PA deadline)\n\nContract assignment: not yet imported — run --contracts to populate\n\nNext step: run \u002Fcorporate-legal:integration-management --contracts to import the\ncontract list, then --report to see your first status summary.\n```\n\n---\n\n## Mode 2: Contract Assignment\n\n```\n\u002Fcorporate-legal:integration-management --contracts [--deal [code]]\n```\n\nThis is the dedicated contract assignment initialization. Separate from the\nmain init so it can be run independently and re-run when the contract list\nchanges.\n\n### Step 1: Get the contract list\n\nTwo paths — use whichever applies:\n\n**Path A: Connected repository**\n\n> Is your contract repository connected? (Google Drive, Box, SharePoint,\n> or a VDR that's still accessible post-close?)\n>\n> If yes: give me the folder path or folder name for the acquired company's\n> contracts. I'll pull a list of what's there and read each contract for the\n> assignment clause and counterparty.\n\nSearch the connected repository. For each document found:\n- Extract filename and file path\n- Read the document — identify: contract party (counterparty name), contract\n  type (from header or subject matter), assignment clause text, change of\n  control clause text if present, and annual value if stated.\n\n**Path B: Manual list upload**\n\n> Upload a contract list. This can be:\n> - The Material Contracts schedule from the PA disclosure schedules\n> - A CSV or Excel export from their contract management system\n> - A manually prepared list\n>\n> Minimum required columns: Contract Name, Counterparty. Helpful but optional:\n> Contract Type, Annual Value, Assignment Clause text.\n\nRead the uploaded list. For contracts where no assignment clause text is\nprovided, set assignment_mechanism to \"not_reviewed\" and flag for follow-up.\n\n**Path C: Disclosure schedule**\n\nIf neither repository nor list is available, read the Material Contracts\nschedule from the PA disclosure schedules (from the PA uploaded in --init).\nThis gives the minimum required list — parties and contract types. Assignment\nclauses will need manual review.\n\n### Step 2: Determine assignment mechanism\n\nFor each contract, classify the assignment mechanism:\n\n| Mechanism | Definition | Tier |\n|---|---|---|\n| `consent-required` | Explicit clause prohibiting assignment without counterparty consent | 1 or 2 |\n| `coc-provision` | Change of control clause giving counterparty termination or consent right triggered by the deal | 3 |\n| `auto-assign` | No restriction, or explicit permission to assign to affiliates or successors | 4 |\n| `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 |\n| `not_reviewed` | Could not read or locate assignment clause | Flag for manual review |\n\nFor contracts flagged in the Required Consents PA schedule: override tier to 1\nregardless of assignment mechanism classification.\n\n### Step 3: Tier assignment\n\n```\nTier 1 — Required Consents: [N] contracts\n  Named in PA schedule, hard deadline [date], must obtain consent\n\nTier 2 — Material, consent required: [N] contracts\n  Assignment restriction present, not in PA schedule\n  Recommended timeline: obtain within Day 90\n\nTier 3 — Change of control provisions: [N] contracts ⚠️\n  Counterparty has termination or consent right triggered by close\n  ACTION REQUIRED: contact counterparty immediately — CoC may already be triggered\n\nTier 4 — Auto-assign \u002F no action: [N] contracts\n  Assigns automatically or by affiliate\u002Fsuccessor provision\n  Tracking only — no outreach needed\n\nNot reviewed: [N] contracts\n  Could not determine assignment mechanism — manual review required\n```\n\nShow tier 3 separately and prominently. A change of control clause may have\nalready triggered on the close date — counterparty may have a right to terminate\nthat is running right now.\n\n### Step 4: Generate status entries\n\nFor each contract, create a tracker entry with:\n- All extracted fields (counterparty, type, value, mechanism, tier)\n- Initial status: tier 4 → `no_action`; tier 3 → `coc_triggered`; tiers 1\u002F2 → `consent_pending`; not_reviewed → `not_reviewed`\n- pa_deadline populated for tier 1 from Required Consents schedule\n\n---\n\n## Mode 3: Status Report\n\n```\n\u002Fcorporate-legal:integration-management --report [--deal [code]]\n```\n\nReads current tracker state. Produces:\n\n```\n[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]\n\n> 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.\n\nINTEGRATION STATUS — [Deal code] \u002F [Target]\n[Date] — Day [N] post-close\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nEXECUTIVE SUMMARY\n[2-3 sentence paragraph: overall status, biggest risk, key win since last report]\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nREQUIRED CONSENTS  [deadline: DATE — N days remaining]\n  Obtained:        [N] of [total]  ████████░░  [%]\n  In negotiation:  [N]\n  Outreach sent:   [N]\n  Not started:     [N]\n  Refused:         [N] ⚠️\n\n⚠️ AT RISK: [counterparty] — deadline in [N] days, no response to outreach\n⚠️ REFUSED: [counterparty] — PA obligation not met; escalate to outside counsel\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nCONTRACT ASSIGNMENT\n  Tier 1 (Required Consents):   [N] complete \u002F [N] in progress \u002F [N] pending\n  Tier 2 (Material contracts):  [N] complete \u002F [N] in progress \u002F [N] pending\n  Tier 3 (CoC provisions):      [N] resolved \u002F [N] outstanding ⚠️\n  Tier 4 (Auto-assign):         [N] — no action required\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nWORKPLAN — LEGAL OWNS\n  🔴 OVERDUE ([N]):\n    [item] — was due [date]\n\n  ⏰ DUE THIS WEEK ([N]):\n    [item] — due [date]\n\n  ✅ COMPLETED SINCE LAST REPORT ([N]):\n    [item] — completed [date]\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nBLOCKERS & DECISIONS NEEDED\n  [item] — blocked on: [description] — owner: [name]\n  [item] — decision needed: [description] — recommend: [option]\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nKEY DATES COMING UP\n  [date] — [milestone \u002F deadline]\n  [date] — Rep survival expires — confirm no pending indemnification claims\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n```\n\n---\n\n## Mode 4: Update\n\n```\n\u002Fcorporate-legal:integration-management --update [--deal [code]]\n```\n\n**Manual update:** Attorney tells Claude what changed.\n\n> \"We got the Salesforce consent. Mark it obtained, assigned to [name], date today.\"\n> \"The entity rationalization decision is to merge. Update status and add the merger\n> filing to Day 180.\"\n> \"[Counterparty] refused consent. Flag it and note we need outside counsel on\n> whether this triggers a PA indemnification claim.\"\n\nClaude updates the relevant tracker entry, recalculates any downstream status\n(e.g., if all tier 1 consents are now obtained, flag the PA obligation as met),\nand shows what changed.\n\n**Upload update:** Workstream owner or outside counsel sends a status document.\n\n> Upload the status update from [outside counsel \u002F HR lead \u002F corp dev team].\n> I'll parse it and update the tracker.\n\nRead the uploaded document. Match described items to tracker entries by\ncounterparty name or workplan item description. Update status fields.\nFlag any items in the update that don't match an existing tracker entry —\nmay be new items to add.\n\nAfter any update, show:\n```\nUpdated [N] items.\n\nChanges:\n  CON-003 Salesforce: not_started → obtained\n  W-014 Entity rationalization: in_progress → complete\n\nNew flags:\n  CON-007 [Counterparty]: refused — PA obligation may be unmet. Consider:\n  outside counsel review of indemnification claim. ⚠️\n```\n\n---\n\n## Mode 5: Export\n\n```\n\u002Fcorporate-legal:integration-management --export [--format csv|table] [--section all|consents|contracts|workplan]\n```\n\nProduces a flat CSV or markdown table. Default: all sections, CSV.\n\nCSV format — one row per item, section indicated by a `section` column.\nColumns vary by section:\n\n*Workplan:* id, phase, description, owner, workstream, priority, deadline, status, blocker\n\n*Consents:* id, counterparty, contract_type, required_consent, pa_deadline, status, assigned_to, obtained_date, notes\n\n*Contracts:* id, name, counterparty, contract_type, annual_value, assignment_mechanism, tier, required_consent, pa_deadline, status, assigned_to, notes\n\nExport is the shareable format — suitable for outside counsel, corp dev, or a\nboard integration update.\n\n---\n\n## What this skill does not do\n\n- It does not manage business integration workstreams (IT, HR, finance, real\n  estate). It tracks legal's touchpoints in those workstreams and flags when\n  legal input is needed. Ownership stays with the business function.\n- It does not draft the consent request letters or novation agreements — those\n  are produced by the written-consent skill or by outside counsel.\n- It does not advise on indemnification claims or PA breach. When a consent is\n  refused or a deadline is missed, it flags the situation — the legal analysis\n  of consequences is the attorney's call.\n- It does not track earn-out performance. Earn-out milestones and payment dates\n  appear in the tracker as reference dates with owner set to finance. The\n  business drives the numbers.\n- It does not read contracts in real time during status reporting. Contract\n  status is what the attorney has updated in the tracker. The skill reads the\n  tracker, not the contracts, at report time.\n\n\n## Formula injection defense\n\nBefore 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 `=`, `+`, `-`, `@`, `\t`, `\n`, or `\n` will be interpreted as a formula or break the row structure.\n\n- **Prefix with a single quote:** `'=SUM(A1:A10)` → `=SUM(A1:A10)` (displayed as text, not executed)\n- **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.\n- **CSV: also escape embedded commas, double quotes, newlines** (RFC 4180 quoting).\n- 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.\n",{"name":5,"description":49,"argument-hint":50},"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\".\n","[--init | --contracts | --report | --update | --export [--format csv|table] [--section all|consents|contracts|workplan]] [--deal [code]]","main","4a6c651889c97cc9140580363c73e0eb17379c2b","corporate-legal\u002Fskills\u002Fintegration-management",1968,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-14 23:30:58",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add anthropics\u002Fclaude-for-legal --skill integration-management",{"tool":65,"command":66},"bunx","bunx skills add anthropics\u002Fclaude-for-legal --skill integration-management",{"tool":68,"command":69},"pnpm","pnpm dlx skills add anthropics\u002Fclaude-for-legal --skill integration-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fcorporate-legal\u002Fskills\u002Fintegration-management\u002FSKILL.md",true,[],[74,104,126,145,166,177],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":85,"publishedAt":44},"01M718SG9G2R92ECCD0HYK2R5E","reg-feed-watcher","Check regulatory feeds now and report what's new since the last check, filtered by your materiality threshold. Use when the user says \"check the feeds\", \"what's new\", \"regulatory update\", when running from the scheduled agent, or when manually pasting a regulatory development for classification and diff.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Freg-feed-watcher\u002FSKILL.md",[80],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[86,87,88,89,90,91,92,93,94,95,96,97,98,99,38,100,101,31,102,103],"reg","watcher","reg feed watcher","running","feeds","filtered","diff","development","for","classification","new","now","use","scheduled","check","last","report","regulatory",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":44},"01M718SCRTBN55DMTVSPG67A7N","policy-redraft","Produce a proposed marked-up policy redraft that closes a gap found by \u002Fregulatory-legal:gaps or \u002Fregulatory-legal:policy-diff. A first draft for internal review — not for direct application to approved policy documents. Use when the user says \"redraft the policy\", \"draft the policy fix\", \"mark up the policy\", or when gap-surfacer hands off a gap for drafting.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fpolicy-redraft\u002FSKILL.md",[],[111,112,92,94,113,114,115,98,116,38,117,118,119,120,121,122,123,124,103,125],"policy","policy redraft","up","fix","produce","documents","drafting","gaps","review","draft","id","gap","mark","first","direct",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":44},"01M718S8RV0C4NMVKG078CBFXP","policy-diff","Diff a specific regulatory change against the indexed policy library. Use when a reg has changed and you need to know which policies it touches and what the gap is, when the user says \"diff this reg against our policies\", \"which policy does this affect\", or \"gap analysis\", or when reg-feed-watcher hands off a material item.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fpolicy-diff\u002FSKILL.md",[],[92,111,133,134,38,135,136,86,137,87,138,139,140,141,98,142,122,143,144,103],"policy diff","which","you","analysis","text","change","paste","library","material","gap analysis","what the","name",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":44},"01M718S6521Y0FT4T24VCFKVG5","matter-workspace","Manage matter workspaces — create, list, switch, close, or detach the active matter (practice-level). Use when working across multiple clients or matters and you need to keep one engagement's context separate from another, or when a substantive skill needs to know which matter it's working in.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fmatter-workspace\u002FSKILL.md",[],[152,153,134,154,155,156,96,98,38,135,157,158,159,160,33,161,162,163,164,165],"workspace","matter workspace","switch","manage","workspaces","keep","across","create","engagement","active","clients","list","it","context",{"skillNo":167,"name":118,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":44},"01M718S3FPEJNQGCMQ1AR8M4HE","Open gaps tracker — what's flagged and not yet closed. Use when the user asks \"what gaps are open\", \"gap tracker\", \"remediation status\", or wants to close (--close GAP-ID) or risk-accept (--accept GAP-ID) a tracked gap.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fgaps\u002FSKILL.md",[],[118,121,122,172,33,32,173,29,174,98,175,38,176],"risk","remediation","open","accept","user",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":184,"publishedAt":44},"01M718S06WSZ9Y24JKYM0VVPPE","gap-surfacer","Reference: shared gap- and comment-tracker framework backing \u002Fregulatory-legal:gaps and \u002Fregulatory-legal:comments. Tracks open policy gaps with remediation status, ingests gaps from policy-diff, surfaces what's open and aging, routes to owners, and notifies gap owners via Slack with per-send confirmation. Loaded by the gaps and comments skills before doing substantive work.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fgap-surfacer\u002FSKILL.md",[183],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[122,185,186,187,92,111,188,174,189,190,191,192,118,193,194,195,196,32,173,197],"gap surfacer","shared","tracks","send","confirmation","aging","false","comments","with","work","slack","via","surfaces"]