integration-management

Initialize and update M&A integration trackers for consents and contract assignments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns scattered deal artifacts and post-closing notes into a structured, time-phased integration tracker that legal can maintain and report on.

Core Features & Use Cases

  • Phased workplan initialization: Builds Day 1/30/90/180 legal workstreams from available inputs such as deal context, closing checklists, and post-closing obligations.
  • Consent and contract assignment tracking: Creates a required-consents tracker with deadlines and a contract assignment tracker with tiering based on consent requirements and change-of-control risk.
  • Status reporting and exports: Generates an executive-ready integration status report and can export tracker data as CSV or tables for outside counsel and stakeholders.
  • Controlled updates from humans or uploaded status docs: Supports manual updates and parsing of uploaded workstream/status documents to keep the tracker current.

Quick Start

Ask the Skill to initialize a new tracker for your deal 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 consents and contract assignments in one place?

Post-closing M&A integration tracking consolidates required consents, contract assignments, and workstreams into an actionable legal tracker. It initializes from deal context and closing checklists, maintaining state in a YAML file to manage deadlines and change-of-control risks.

What is the best way to build a Day 1 to Day 180 M&A legal integration workplan?

Building a phased M&A legal integration workplan involves initializing a tracker from available inputs like purchase agreements and closing checklists. The tracker generates time-phased Day 1, 30, 90, and 180 legal workstreams for ongoing updates and reporting.

Can I export M&A integration tracker data to CSV for outside counsel?

Yes, you can export M&A integration tracker data as CSV or tables for outside counsel and stakeholders. The export functionality includes spreadsheet formula injection defenses to ensure secure data sharing and executive-ready status reporting.

Do I need closing checklists and purchase agreements to initialize an M&A integration tracker?

No, you do not need specific artifacts to initialize an M&A integration tracker. The system applies to deal teams with varying inputs, supporting initialization from purchase agreements, deal summaries, closing checklists, contract lists, or even no initial documents.

How do I keep an M&A integration tracker current with uploaded status documents?

Updating an M&A integration tracker supports controlled manual updates and parsing of uploaded workstream status documents. This ensures the tracker remains current by routing workflow updates through specific flags to maintain accurate reporting.

What are the limitations of using YAML for M&A integration management state tracking?

Using YAML for M&A integration management state tracking requires routing workflow through specific flags like --init, --contracts, --report, --update, and --export. It is not a traditional spreadsheet, meaning CSV exports are generated on demand rather than offering live spreadsheet editing.