Draft Markup Of Counterparty Postnuptial Agreement

---
name: draft-markup-of-counterparty-postnuptial-agreement
task_id: trusts-estates-private-client/draft-markup-of-counterparty-postnuptial-agreement
description: Producing an article-by-article redline markup of a proposed postnuptial agreement requires identifying provisions that are asymmetric, undisclosed, or potentially unconscionable, and replacing them with client-protective language accompanied by explanatory commentary.
activates_for: [planner, solver, checker]
---

# Skill: Draft Markup of Counterparty Postnuptial Agreement with Attorney Commentary

## 1. Subject-matter triage

- Treat the proposed agreement, the background materials, and any transmittal communications as one integrated drafting record.
- Identify the governing-law baseline, any disclosure package, and any timeline pressure before revising text.
- If there is more than one spouse, asset class, business interest, or disclosure package at issue, enumerate each before drafting so no category is merged by assumption.
- If the deliverable requires a file, create the final markup document first and ensure it contains operative revised clauses before preparing any cover note or summary.

## 2. Failure modes the skill is correcting

- Flagging a problem without supplying replacement contract language.
- Producing a redline that depends only on visual formatting instead of text that survives export.
- Missing the combined effect of individually modest edits that, together, shift the agreement’s economics.
- Omitting commentary that explains why the proposed revision protects the client.
- Overlooking clauses that operate through silence, deemed acceptance, waiver by inaction, or one-sided notice deadlines.
- Treating disclosure, valuation, or amendment provisions as boilerplate when they control enforceability and leverage.
- Discussing legal conclusions without naming the governing rule or authority.
- Failing to end with concrete next steps for the client team.

## 3. Legal frameworks / domain conventions that apply

- Postnuptial agreements are tested for voluntariness, disclosure, and substantive fairness under the governing state law for marital agreements, including any heightened scrutiny applicable to post-marriage execution.
- Disclosure provisions should preserve mutual, meaningful financial disclosure and should not contract away ordinary verification rights unless the client knowingly accepts that risk.
- Asymmetry matters: provisions that treat one spouse, one asset class, or one valuation event differently should be made symmetric unless the client receives a clear negotiated benefit.
- Business-interest and valuation mechanics are economically material; date of valuation, methodology, and expert selection should be neutral or jointly controlled rather than unilateral.
- Amendment, waiver, and deemed-acceptance provisions should require express mutual written agreement; silence should not function as consent.
- Any legal proposition used in the markup or commentary should be anchored to the controlling governing-law source, such as the relevant statute, regulation, rule, or leading case identified for the engagement.
- Any fairness or enforceability critique should be tied to the specific doctrine supporting it, not stated as a bare conclusion.

## 4. Analytical scaffolds

1. Read the agreement article by article and ask, for each provision: what it does economically, whether it is symmetric, whether it is disclosure-sensitive, whether it is valuation-sensitive, and whether any transmittal text misdescribed it.
2. For each material issue, draft replacement language rather than only deletion marks; pair the language with a concise rationale.
3. Analyze the agreement cumulatively, not provision by provision in isolation; note when several small provisions collectively create a one-sided result.
4. For any clause that amends rights by silence, waiver, deadline, or automatic adoption, replace it with a mutual written-consent standard.
5. For any disclosure limitation, restore ordinary access to confirmatory information or explain the negotiated limitation if retained.
6. For any valuation clause, prefer a neutral method, a jointly selected expert, or an agreed process that limits one party’s unilateral control.
7. When multiple alternatives exist, state the preferred client position and any fallback position separately.
8. Frame each comment as: issue, risk, proposed change, and client-protective effect.

## 5. Vertical / structural / temporal relationships

- Preserve the agreement’s article-by-article architecture so the markup maps cleanly to the base document.
- Within each article, move from threshold edits that affect enforceability or economics to drafting refinements.
- Flag temporal traps, including notice windows, objection periods, election deadlines, execution timing, disclosure cutoffs, and valuation dates.
- Where a later provision overrides an earlier one, note the hierarchy and ensure the later provision does not silently erode the earlier protection.
- In the cover commentary, summarize which points are negotiation anchors and which are opening positions, using general negotiating language rather than a document synopsis.

## 6. Output structure conventions

- Produce a complete article-by-article redline markup in a format that remains intelligible after conversion.
- Mark every substantive change with explicit textual tags such as [DELETED: …], [INSERTED: …], or [REPLACED: old → new], even if styling is also used.
- Attach a short [Rationale: …] immediately to each substantive change so the reader can identify the issue from plain text alone.
- For each material comment, include an ordinal severity label defined once at the top of the commentary, and use that label consistently.
- Use severity labels that are genuinely ordinal, not descriptive substitutes.
- If the document contains several distinct provisions of the same type, address each one separately rather than using a representative example.
- Keep the markup and commentary integrated article by article; do not rely on a separate standalone issues list as a substitute for drafting.
- End with a concise Recommended Actions section that tells the client team what to do next, who should do it, and when relative to signing or negotiation.
- Before finalizing, confirm that the primary deliverable file exists, is non-empty, and contains the operative markup rather than a summary of what should be marked.