integration-management

Build and update a deal-specific M&A integration tracker with workplan items and consents.

100|16|Updated May 13, 2026
One-click install
npx skills add https://github.com/ZekaiSuni/claude-for-legal-turkish --skill integration-management-zekaisuni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration-management
Source: https://github.com/ZekaiSuni/claude-for-legal-turkish/tree/main/corporate-legal/skills/integration-management
Command: npx skills add https://github.com/ZekaiSuni/claude-for-legal-turkish --skill integration-management-zekaisuni

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deals often have post-closing work that gets delayed or missed, especially when consents, contract assignments, and statutory deadlines depend on multiple counterparties. This Skill helps you keep a legally-driven integration tracker up to date right after closing, based on the deal context and SPA/covenants.

Core Features & Use Cases

  • Post-closing integration workplan management: Creates and maintains a 1/30/90/180-day legal workplan (legal owns/supports, priorities, deadlines, dependencies, and blocker notes).
  • Consent tracking (required vs desired): Imports/initializes consent items from the SPA context, records outreach/negotiation/obtained/waived/refused states, and flags the last required-consent deadline.
  • Contract assignment classification & status: Imports contract lists and categorizes assignment mechanisms (e.g., consent-required, change-of-control provision, auto-assign, silent) into tiered buckets for reporting and follow-up.
  • Status reporting, update intake, and export: Generates an attorney-facing status report, ingests uploaded update material to reconcile against tracker items, and exports CSV/table sections for outside counsel or governance updates.

Quick Start

Run the integration tracker initialization for a specific deal code so you get a ready-to-fill post-closing workplan and consent/covenant structure, then view the first status report.

Frequently Asked Questions about integration-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track post-closing M&A legal integration and required consents?

You can track post-closing M&A legal integration by building a deal-specific tracker that structures your 1/30/90/180-day workplan. It manages required consent outreach timelines, records contract assignment tiers, and ensures statutory deadlines across counterparties are met.

What is the best way to classify contract assignment tiers after an acquisition?

Classifying contract assignment tiers involves categorizing mechanisms into consent-required, change-of-control provision, auto-assign, and silent buckets. This classification helps legal teams prioritize follow-ups and manage novation obligations systematically during post-closing integration.

How do you record and manage consent tracking states for SPA covenants?

Consent tracking states for SPA covenants are recorded by logging outreach, negotiation, obtained, waived, or refused statuses. This process flags the last required-consent deadline and relies on a structured YAML tracker to preserve data schema conventions during updates.

Can I generate attorney-facing status reports and exports from a YAML integration tracker?

Yes, generating attorney-facing status reports and CSV exports from a YAML integration tracker is supported. The system ingests uploaded update materials to reconcile against workplan items and produces actionable status reports for outside counsel.

Does post-closing integration management support mode-based execution for specific deal codes?

Yes, post-closing integration management supports mode-based execution for specific deal codes. By reading deal-context and closing-checklist inputs, it initializes a ready-to-fill workplan and writes updates directly to the canonical YAML tracker path.