integration-management

Build and maintain phased M&A integration trackers with consent status and contract tiers.

Updated May 26, 2026
One-click install
npx skills add https://github.com/yachela/claude-for-legal-ar --skill integration-management-yachela
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration-management
Source: https://github.com/yachela/claude-for-legal-ar/tree/main/corporate-legal/skills/integration-management
Command: npx skills add https://github.com/yachela/claude-for-legal-ar --skill integration-management-yachela

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integration-management removes the chaos of post-closing M&A legal work by turning scattered deal artifacts into a single, actionable integration tracker with clear deadlines, consent status, and contract assignment progress.

Core Features & Use Cases

  • Phased integration workplan builder: Creates Day 1 / Day 30 / Day 90 / Day 180 legal-owned and legal-supports tasks, inheriting items from the M&A cold-start closing checklist when available.
  • Consent tracking tied to PA deadlines: Extracts Required Consents (and deadlines) from the purchase agreement when provided, then maintains outreach and status progression.
  • Contract assignment triage at scale: Imports or ingests a contract list, classifies assignment mechanism and change-of-control triggers, assigns tiers, and supports recurring updates and reporting.
  • Operational reporting and exports: Generates a status report (workplan + consents + contract tiers) and exports the tracker to CSV or tables with formula-injection defenses for spreadsheet outputs.

Quick Start

Use integration-management to initialize a post-closing tracker from your deal code and available deal artifacts by running: /corporate-legal:integration-management --init --deal CODE

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 integration tasks and required consents?

Track post-closing M&A integration by building a phased workplan that monitors Day 1 to Day 180 legal tasks, required consent outreach, and contract assignment tiers within a single tracker file.

How do I build a phased integration workplan after an acquisition closes?

Build a phased integration workplan by initializing a post-closing tracker that generates Day 1, Day 30, Day 90, and Day 180 legal-owned and legal-supports tasks, inheriting items from a closing checklist.

What is the best way to triage contract assignments and change-of-control triggers at scale?

Triage contract assignments by importing a contract list to classify assignment mechanisms and change-of-control triggers, assign progress tiers, and support recurring status updates and reporting.

Can I export M&A integration status reports to a CSV file?

Export M&A integration status reports to CSV or tables by generating a combined report of workplan progress, consent statuses, and contract tiers with spreadsheet-safe output handling and formula-injection defenses.

Does integration management require specific deal artifacts to initialize?

Initialization requires reading a deal-context.md file and an optional closing-checklist.yaml to create or update an integration-tracker.yaml under the deal workspace, enforcing role-appropriate context.

How are required consent deadlines tracked during post-close integration?

Required consent deadlines are tracked by extracting them from the purchase agreement when provided, then maintaining ongoing outreach and status progression within the integration tracker.