# Hls Draft Markup Healthcare Merger Agreement > Produces a healthcare merger agreement markup commentary and issues summary chart that contextualizes each issue against the applicable negotiation playbook, incorporates cross-document references from related compliance and financing materials when they bear on the provision being analyzed, and applies a structured issue-analysis framework. - Skill: `finchipaiorg/hls-draft-markup-healthcare-merger-agreement` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/hls-draft-markup-healthcare-merger-agreement` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/hls-draft-markup-healthcare-merger-agreement/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: FinchipAIOrg (https://skillmd.com/u/finchipaiorg) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/finchipaiorg/hls-draft-markup-healthcare-merger-agreement --- # Skill: Draft Markup of Healthcare Merger Agreement with Regulatory Commentary ## 1. Subject-matter triage - Treat the merger agreement as the primary document to analyze against the playbook, compliance summary, commitment letter, and partner instructions. - If the source set contains multiple deals, entities, approval tracks, or seller groups, enumerate them first and analyze each separately before synthesizing. - If a provision depends on timing, regulatory approval, or disclosure status, anchor the analysis to the specific closing sequence and any stated outside date or renewal milestone. - If the draft is a true markup task, preserve the agreement’s operative structure while identifying where the text should change and why. ## 2. Failure modes the skill is correcting - Issues are identified in isolation rather than tied to the playbook benchmark, the related document, and the business consequence. - Compliance and financing materials are ignored even when they change disclosure, covenant, approval, or risk allocation analysis. - Healthcare-specific risk is flattened into generic M&A commentary instead of being linked to reimbursement, licensure, fraud-and-abuse, physician arrangements, and regulatory approvals. - The commentary states conclusions without naming the authority, clause interaction, or practical consequence that supports them. - Markup comments describe the problem but do not tell the drafter what to change, who should act, or when. - Severity is implied rather than stated, making the priority of fixes hard to triage. ## 3. Legal frameworks / domain conventions that apply - Use the governing healthcare regulatory framework reflected in the source materials, including federal fraud-and-abuse law, physician arrangement rules, reimbursement program constraints, licensure requirements, and state approval regimes. - Where a corporate integrity agreement, settlement obligation, monitoring protocol, reporting duty, or exclusion risk is disclosed in the source set, treat it as a live contractual and regulatory input to representations, covenants, closing conditions, and bring-downs. - When a representation concerns healthcare compliance, distinguish among general compliance, specific program participation, physician compensation, referral relationships, billing practices, and safe-harbor or exception coverage. - For facility licensure and certificate-type approvals, distinguish exempt and non-exempt facilities and tie the analysis to the relevant state regime and closing timeline. - For termination economics, compare the draft to the playbook benchmark and state the practical departure in ordinary terms rather than only by descriptor. - For rollover or continuing equity held by physicians or other providers, assess governance, transfer, vesting, and special rights separately from the standard acquisition mechanics. - For regulatory approval timing, assess whether the outside date and interim covenants accommodate the longest expected review path and any renewal requirement that could block closing. - Cite the controlling authority or source basis for each legal proposition or regulatory conclusion, using the statute, regulation, rule, doctrine, or source document as identified in the record. ## 4. Analytical scaffolds - For each issue, work in this order: identify the draft language or omission; state the playbook or source-document requirement; describe the deviation; explain the risk; and give a concrete recommended revision. - Tie each issue to a material figure, threshold, deadline, approval step, exposure bucket, or other scale from the source documents when available. - Cross-reference the other clause, schedule, compliance item, financing term, or instruction that interacts with the issue before recommending a fix. - State the downstream consequence in business, regulatory, litigation, operational, or transaction terms so the reader can triage the issue quickly. - If multiple parties, facilities, reimbursement streams, or approval tracks are in scope, analyze each one separately rather than using a generic representative example. - For any healthcare compliance representation, specify the applicable exception, safe harbor, or analogous protection where the source record supports it, and include a closing bring-down concept if timing matters. - For any disclosure of a compliance agreement or settlement-driven obligation, describe the actual obligations, reporting cadence, monitoring duty, and exclusion or default risk that make it material. - For any approval or licensing issue, test the stated outside date against the approval process and likely review duration, not just against an abstract closing preference. - For any physician rollover issue, identify the holder group and describe the separate contractual rights that need to be preserved or harmonized. - For each identified issue, assign an explicit severity using one ordinal scale defined once and applied consistently throughout the memo, such as Critical / High / Medium / Low. - End each issue with a recommendation that states the action, the responsible role, and the timing anchor tied to the deal or regulatory milestone. ## 5. Vertical / structural / temporal relationships - Map how the agreement, playbook, compliance summary, commitment letter, and partner instructions interact before finalizing any commentary. - If the compliance summary contains ongoing obligations, reconcile them with reps, covenants, conditions, and termination triggers in the draft. - If the commitment letter imposes funding, diligence, cooperation, or approval-related conditions, assess whether the merger agreement aligns with those constraints. - If partner instructions override or refine the playbook, treat them as controlling for the commentary and reflect the resulting negotiation priority. - If the transaction timeline includes renewal dates, approval periods, or external review windows, evaluate the agreement’s closing mechanics against that sequence. - Where the source materials create a hierarchy of obligations, note the controlling source and the clause that should yield or be tightened. ## 6. Output structure conventions - Produce two deliverables: a prioritized commentary memo and an issues summary chart. - In the commentary memo, define the severity scale once at the top, then present issues in priority order. - For each issue, include: severity; the draft position; the applicable playbook or source benchmark; the deviation; the risk and source-based consequence; the cited authority or source basis; and the recommended revision. - Use industry-conventional headings and prose, not the rubric’s internal section labels. - Keep the memo concise but complete; every issue must close the analytical loop and end with a concrete recommendation. - In the issues summary chart, use a tabular format with columns that capture the issue, severity, playbook or source deviation, and recommendation. - Ensure the summary chart mirrors the memo’s prioritization and uses the same severity labels. - If the task requires drafting/redlining language in addition to commentary, mark each substantive change in text with a plain-text convention that survives export, and attach a short rationale to each change.