Analyze Counterparty Markup Of Prenuptial Agreement

---
name: analyze-counterparty-markup-of-prenuptial-agreement
task_id: trusts-estates-private-client/analyze-counterparty-markup-of-prenuptial-agreement
description: Redline analysis of a counterparty's prenuptial agreement markup requires systematic tracking of every change against the client's original draft and financial disclosures, with attention to asymmetric provisions, cross-provision interactions, and enforceability risks.
activates_for: [planner, solver, checker]
---

# Skill: Analyze Counterparty Markup of Prenuptial Agreement — Redline Analysis Memorandum

## 1. Subject-matter triage

- Identify the governing jurisdiction and the agreement’s enforceability framework before analyzing substantive edits.
- Determine whether the redline involves one agreement or multiple versions/iterations; if more than one markup exists, enumerate each version and analyze them separately.
- Separate provisions that affect property characterization, disclosure, support, dispute resolution, and execution formalities, since each can change enforceability and economics in different ways.

## 2. Failure modes the skill is correcting

- Relying on the counterparty’s summary instead of independently mapping every addition, deletion, substitution, and moved clause in the redline.
- Treating the markup as a set of isolated edits and missing how revisions to one clause can negate, amplify, or create ambiguity in another.
- Failing to test the agreement against disclosure, voluntariness, independent counsel, and unconscionability requirements under the applicable premarital agreement statute.
- Missing asymmetry: a clause that appears facially reciprocal may be economically one-sided once the parties’ asset mix, liquidity, earnings profile, and expected appreciation patterns are considered.
- Overlooking execution or process defects, such as incomplete schedules, weak acknowledgment language, or timing pressure around signing.
- Describing risk without stating what in the source documents makes the issue material, how it interacts with another clause, and what practical consequence follows for the client.

## 3. Legal frameworks / domain conventions that apply

- Premarital agreements are commonly assessed under the applicable state act or statute governing validity, disclosure, voluntariness, and unconscionability; cite the controlling state statute and section used in the file.
- Financial disclosure adequacy is often a predicate issue: the agreement should be measured against the listed assets, liabilities, income, and expected liquidity events in the disclosure materials.
- Independent counsel and informed waiver language matter because they can affect enforceability even where the substantive economics are aggressive.
- Property characterization provisions should be read for consistency between separate property, marital property, commingling, transmutation, and appreciation treatment.
- Appreciation clauses require careful distinction between passive appreciation and appreciation attributable to marital labor, management, or marital funds.
- Spousal support provisions should be analyzed as a package: amount, duration, trigger events, waiver language, and modification standards can interact.
- Dispute resolution clauses, including arbitration or forum-selection language, may be enforceability-sensitive depending on jurisdiction and should be tested against the governing act and general arbitration law.
- Sunset, expiration, or step-down clauses can materially shift the economic bargain over time and can affect the durability of other protective provisions.

## 4. Analytical scaffolds

1. Map every substantive change in the redline, including edits that move text, rename defined terms, or alter cross-references.
2. For each change, identify the advantaged party, the economic significance of the shift, and whether the change is facially symmetric but substantively asymmetric given the disclosed asset profile.
3. For each issue, tie the analysis to a concrete source-document metric or threshold where available: asset class, liquidity event timing, support term, disclosure scope, or exposure created by the edit.
4. Cross-check whether a change in one clause depends on, overrides, or conflicts with another clause, schedule, exhibit, disclosure statement, or signature block.
5. Test whether the redline weakens disclosure verification, narrows representations, broadens waivers, or introduces ambiguity that could undermine enforceability.
6. Evaluate appreciation language for internal consistency: confirm whether the text distinguishes active from passive appreciation, addresses marital contributions, and preserves the intended separate-property treatment.
7. Review support provisions as an integrated package rather than piecemeal edits; a change to duration may matter more when paired with a cap, carve-out, or trigger change.
8. If the source set contains more than one version, scenario, or party position, analyze each one explicitly and do not collapse distinct edits into a single pass.
9. Cite the controlling authority for each legal proposition relied on, including the governing premarital agreement statute, relevant arbitration authority, or other cited rule as applicable.
10. Close each issue with the practical consequence for the client and a concrete recommendation, not just a description of the edit.

## 5. Vertical / structural / temporal relationships

- Read the agreement vertically across definitions, operative provisions, schedules, and execution pages to see whether a changed term propagates through the document.
- Read horizontally across related clauses to detect offsetting edits, such as a limitation in one provision paired with a broader waiver in another.
- Track temporal effects where the same clause behaves differently before marriage, during marriage, upon separation, at death, or upon a liquidity event.
- Treat timing-sensitive events, especially imminent financings, sales, vesting, or other liquidity triggers, as potentially material to classification and leverage.
- Flag when a later clause silently overrides an earlier one, or when an amended definition changes the meaning of an unamended operative section.
- Where the agreement references external disclosures or exhibits, verify that the referenced materials are complete and consistent with the redline.

## 6. Output structure conventions

- Use a concise memorandum format with a short executive summary, followed by issue-by-issue analysis ordered by practical importance.
- Define an ordinal severity scale once at the top and apply it consistently to every issue.
- For each issue, include:
  - the change made in the markup,
  - the affected party or parties,
  - the severity rating,
  - the source-document basis for materiality,
  - the controlling authority or governing rule,
  - the cross-provision interaction, if any,
  - the downstream consequence for the client,
  - the recommended response.
- Include a short section that notes any cover-letter or transmittal mismatches with the actual markup, but do not rely on the cover letter as a substitute for issue mapping.
- Include a separate cross-provision interaction section when one edit affects another clause’s operation or meaning.
- Include an enforceability section addressing disclosure adequacy, voluntariness, counsel, formalities, and statutory compliance.
- End with a Recommended Actions block that assigns each action to a responsible role and ties it to a practical timing anchor.
- If preparing the redline itself as part of the work product, mark each substantive change with durable plain-text conventions in addition to any styling, so the change is readable even if formatting is lost.
- Confirm in the completed work that the operative memo is complete and that no issue is left without severity, authority, consequence, and next step.