Producing a prioritized redline markup of a draft prenuptial agreement requires identifying asymmetric and over-broad provisions unfavorable to the client, supplying replacement contract language, and embedding commentary explaining the legal basis and strategic rationale for each change.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add sunyifeisb-art/legalwork --skill draft-markup-of-counterparty-prenuptial-agreement --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Draft Markup Of Counterparty Prenuptial Agreement?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sunyifeisb-art-draft-markup-of-counterparty-prenuptial-agreement)More formats (shields.io, HTML) on the badges page.
---
name: draft-markup-of-counterparty-prenuptial-agreement
task_id: trusts-estates-private-client/draft-markup-of-counterparty-prenuptial-agreement
description: Producing a prioritized redline markup of a draft prenuptial agreement requires identifying asymmetric and over-broad provisions unfavorable to the client, supplying replacement contract language, and embedding commentary explaining the legal basis and strategic rationale for each change.
activates_for: [planner, solver, checker]
---
# Skill: Draft Markup of Counterparty Prenuptial Agreement with Commentary
## 1. Subject-matter triage
- Treat the client intake, financial declarations, and strategy notes as the controlling inputs for priority, leverage, and non-negotiables.
- Identify whether the draft is one spouse-favorable or balanced; if the scope includes multiple versions, jurisdictions, or signing scenarios, enumerate them before analysis and handle each separately.
- Write the markup as the primary deliverable; do not defer substantive changes into a separate memo that would leave the agreement itself unworked.
## 2. Failure modes the skill is correcting
- Flagging adverse provisions without drafting replacement language that can be dropped into the agreement.
- Giving uniform treatment to all issues instead of ranking essential changes ahead of bargaining positions.
- Missing how one clause shifts the meaning or risk of another, especially around disclosure, property characterization, support, enforcement, and dispute resolution.
- Treating disclosure as a side issue rather than a core enforceability condition.
- Using only visual redline styling that may not survive export; the change must remain legible from the text alone.
- Stating conclusions without anchoring them to the governing premarital-agreement framework or other controlling authority.
## 3. Legal frameworks / domain conventions that apply
- Premarital agreement enforceability turns on the applicable state framework governing voluntariness, independent counsel, disclosure, unconscionability, and timing; commentary should tie each proposed fix to the governing rule.
- Separate property and marital property definitions should be checked for symmetry, internal consistency, and whether appreciation, income, and contributions are allocated in a one-sided way.
- Earnings during marriage, passive appreciation, business growth, trust interests, and commingling provisions often drive the economic outcome more than the headline property clause.
- Waivers or limitations of spousal support must be tested against the applicable statute and case law, including any limitations on unconscionable outcomes at enforcement.
- Sunset, review, amendment, and termination mechanics should be evaluated for how they shift bargaining power over time.
- Arbitration, venue, attorney-fee, choice-of-law, and severability provisions can materially affect enforceability and negotiation leverage.
- Disclosure schedules, verification rights, acknowledgments, and certifications support defensibility only if they are complete and internally matched to the operative definitions.
- Cite the controlling statute, regulation, rule, or leading case whenever the markup commentary relies on a legal proposition.
## 4. Analytical scaffolds
1. Review the draft clause by clause and classify each issue by symmetry, enforceability risk, economic impact, and interaction with related provisions.
2. For each issue, determine the client impact using the financial declarations and strategy notes; explain why the term matters in the real balance sheet, not just in drafting form.
3. Convert every material objection into substitute language that preserves negotiation momentum while protecting the client.
4. Apply an ordinal severity scale defined once at the top of the markup, such as Critical / High / Medium / Low, and use it consistently for every comment.
5. Close every comment with three elements: the legal or financial risk, the cross-reference to the related clause or schedule, and the downstream consequence for the client.
6. When the draft or the source set presents multiple parties, periods, elections, or scenarios, analyze each separately rather than collapsing them into a single representative treatment.
7. For every substantive redline, use plain-text markers that survive export, alongside any tracked-changes styling, so the replacement can be read even if formatting is lost.
8. Add a short rationale block to each substantive change that states the issue, the proposed fix, and whether the change is essential or a negotiating position.
9. End with a practical recommendations section that assigns next steps to counsel or the relevant client-side decision-maker and ties each step to a timing anchor from the deal process or the signing timeline.
## 5. Vertical / structural / temporal relationships
- The strategy notes control priorities; the financial declarations control magnitude and sensitivity; the draft controls where to operate.
- Disclosure adequacy, waiver scope, and support provisions should be read together because fixing one may require conforming edits in acknowledgments, schedules, or survival language.
- Property characterization at signing can cascade into later income, appreciation, reimbursement, and commingling treatment.
- Timing matters: pre-signing disclosure, counsel review, execution formalities, and any post-signing review or amendment windows should be reconciled so the commentary does not propose a fix that fails procedurally.
## 6. Output structure conventions
- Produce a prioritized markup of the agreement itself as the primary output file, with embedded commentary at each material edit point.
- Use robust textual conventions for every substantive change, such as [DELETED: …], [INSERTED: …], and [REPLACED: old → new], even if tracked changes are also used.
- For each comment, include: severity, issue statement, proposed language or replacement concept, legal basis with authority, cross-reference to the affected clause or schedule, and client consequence.
- Distinguish essential edits from negotiation points, and say so expressly in the commentary.
- Keep the markup readable as a standalone document; the reader should be able to identify the proposed changes without consulting a separate memo.
- Conclude with an explicit Recommended Actions section that lists the next drafting, review, and approval steps, assigns them to the relevant role, and ties them to the signing or negotiation milestone.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!