Analyze Counterparty Markup Of Merger Agreement

---
name: hls-analyze-counterparty-markup-merger-agreement
task_id: healthcare-life-sciences/analyze-counterparty-markup-of-merger-agreement
description: Reviews a counterparty's redline of a merger agreement against the initial draft and related deal materials to identify compounded risk interactions, representation issues, and asymmetric risk allocation with term-sheet deviation analysis.
activates_for: [planner, solver, checker]
---

# Skill: Analyze Counterparty Markup of Merger Agreement

## 1. Subject-matter triage

- Treat the task as a comparison-and-advice exercise across the initial draft, the counterparty markup, and attached deal documents.
- First identify whether the markup is singular or whether multiple versions, counterparties, or negotiated strands are in scope; if multiple are present, separate them before analysis.
- If the task is delivered as a memo, preserve the memo as the analysis vehicle and do not displace it with a pure issue list.
- If the task also requires producing a marked draft, complete the marked draft first and only then the memorandum.

## 2. Failure modes the skill is correcting

- Individual edits are cataloged without connecting them to economic, regulatory, operational, or transaction-certainty consequences.
- Changes are described without mapping them to the term sheet, ancillary documents, or the governing draft hierarchy.
- Counterparty edits are treated as isolated points instead of interdependent shifts in leverage, closing risk, or post-closing exposure.
- Severity is implied informally instead of being stated consistently and comparably across issues.
- The analysis notes a concern but stops short of a concrete recommendation, timing anchor, or responsible actor.
- Redline commentary relies on formatting alone and becomes unreadable when exported or copied.
- Issues are stated as legal conclusions without naming the governing provision, market convention, or doctrinal basis supporting the point.

## 3. Legal frameworks / domain conventions that apply

- Compare the markup against the agreed transaction package, including the draft merger agreement, disclosure schedules, term sheet, board materials, and any side letters or ancillary drafting instructions.
- Read deviations through merger-agreement conventions that commonly allocate closing risk: MAE / material adverse effect, regulatory approval efforts, financing conditions, specific performance, termination fee structure, interim operating covenants, go-shop mechanics, and tax-opinion conditioning.
- Treat narrowing carve-outs, strengthening buyer outs, weakening seller protections, or shifting consent rights as possible reallocations of deal certainty, even where the clause remains facially market.
- In regulated or product-development-heavy businesses, give special attention to representations, covenants, and closing conditions tied to product status, compliance, data integrity, approvals, manufacturing, supply, or pipeline conduct.
- Distinguish legal significance from drafting preference: a change matters most when it departs from the agreed economics, changes closing leverage, or creates a new mismatch with another document in the package.
- When invoking a legal proposition, cite the controlling authority, rule, statute, regulation, or generally recognized transactional convention that supports the proposition.
- Use the governing law and deal-doc hierarchy to explain whether the markup changes the operative bargain or merely clarifies it.

## 4. Analytical scaffolds

1. For each issue, state: original text or position, counterparty change, why the change matters, how it departs from the agreed package, and the recommended response.
2. Close each issue by tying it to a scale or figure from the source set where possible, then cross-reference the interacting provision, and then state the downstream consequence for the client.
3. Apply an ordinal severity field to every issue using one consistent scale defined once at the top of the memo.
4. Prioritize deviations from the agreed deal terms over ordinary market flexibility questions.
5. Group related edits into compound risk clusters where provisions interact and amplify one another.
6. Track whether the change increases or decreases seller protection, buyer certainty, regulatory burden, or post-closing exposure.
7. Distinguish drafting clarifications from true substantive shifts in allocation of risk.
8. Where the markup touches tax opinions, closing conditions, or enforcement rights, test the opinion standard, obligor, and practical ability to close under the revised language.
9. If the same issue appears in multiple sections, analyze the operative effect once and note all affected locations rather than repeating a separate full analysis each time.
10. Keep any redline markup legible in plain text by using explicit textual change markers and a short rationale for each substantive edit.

## 5. Vertical / structural / temporal relationships

- Read closing conditions, termination rights, and specific-performance language together because changes in one clause can alter the practical value of the others.
- Read MAE definitions alongside interim covenants and indemnity / survival concepts where the deal package uses the same concept across pre-closing and post-closing risk allocation.
- Read financing-related conditions, reverse termination mechanics, and enforcement provisions as an interdependent cluster.
- Read representation qualifiers, disclosure schedules, and bring-down language together to identify whether a concession in one place is offset or undone elsewhere.
- Read go-shop and no-shop mechanics together with breakup fee and fiduciary-out language to determine whether the marketing process remains commercially workable.
- Read any regulatory-efforts covenant together with the timing of filings, consultation rights, and closing triggers so the memo captures practical delay risk, not just formal language changes.

## 6. Output structure conventions

- Start with a brief executive summary that identifies the highest-impact changes and the overall risk posture.
- Define the severity scale once near the top and apply it uniformly to every issue entry.
- Present issues in descending severity, but keep compound clusters together when their combined effect is more important than their individual pieces.
- For each issue entry, use a consistent template: severity; clause or location; original position; markup change; analysis; interaction with other provisions; consequence; recommended position.
- Include explicit change notation in any quoted or paraphrased redline discussion so the reader can identify the edit from plain text alone.
- Where helpful, separate issues into buckets such as risk allocation, closing conditions, interim covenants, disclosure / reps, remedies, fees, and process mechanics.
- End with a Recommended Actions section that gives an imperative, assigns the responsible role from the deal documents or instruction set, and ties the action to a milestone or urgency point in the transaction timeline.
- Conclude with a concise compounding-risk section that explains how the main edits interact and whether the combined effect materially changes deal certainty or leverage.