Closes the gap where agents identify surface-level prenuptial issues without challenging the adequacy of financial disclosure, flagging relevant enforcement considerations, assessing maintenance waiver unconscionability risk, and identifying provisions that may be unenforceable or overbroad.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add sunyifeisb-art/legalwork --skill identify-issues-in-counterpartys-draft-prenuptial-agreement --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Identify Issues In Counterpartys Draft Prenuptial Agreement?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sunyifeisb-art-identify-issues-in-counterpartys-draft-prenuptial)More formats (shields.io, HTML) on the badges page.
---
name: identify-issues-in-counterpartys-draft-prenuptial-agreement
task_id: trusts-estates-private-client/identify-issues-in-counterpartys-draft-prenuptial-agreement
description: Closes the gap where agents identify surface-level prenuptial issues without challenging the adequacy of financial disclosure, flagging relevant enforcement considerations, assessing maintenance waiver unconscionability risk, and identifying provisions that may be unenforceable or overbroad.
activates_for: [planner, solver, checker]
---
# Skill: Identify Issues in Counterparty's Draft Prenuptial Agreement
## 2. Failure modes the skill is correcting
- Accepting one party's disclosure as sufficient without testing it against the other party's disclosure set and supporting records.
- Treating owner-supplied values for a business interest as adequate absent supporting statements, appraisals, tax filings, or other verifiable backup.
- Missing the enforcement risk created by a broad support waiver that is not narrowed by duration, dependence, or other limiting features.
- Overlooking that enforceability standards can change materially with the governing law clause and the parties' likely domicile or forum.
- Failing to flag overreaching terms that attempt to control residence, modification, debt allocation, or similar matters in a way many jurisdictions will not enforce.
- Stopping at description of the clause instead of tying the issue to the controlling doctrine, the related agreement provisions, and the client-side consequence.
- Producing recommendations without a severity ranking or without a clear next step.
## 3. Legal frameworks / domain conventions that apply
- Prenuptial enforceability is commonly analyzed under the Uniform Premarital Agreement Act or comparable state law, with variation on whether unconscionability is tested at execution, at enforcement, or both; involuntariness and inadequate disclosure remain central challenge points.
- Adequate financial disclosure ordinarily means disclosure of the nature and approximate value of assets and liabilities, with enough supporting material for the other party to evaluate the disclosure meaningfully.
- A self-set value for a closely held business, standing alone, is often weaker than disclosure supported by financial statements, tax returns, or an independent appraisal.
- A complete waiver of maintenance or spousal support may be permissible in some settings but can be vulnerable if enforcement would be unconscionable in light of the marriage’s duration, the parties’ economic dependence, or post-marriage circumstances.
- Choice-of-law and forum-related provisions can materially affect the governing enforceability standard; identify which jurisdiction likely controls and whether that helps or hurts the intended position.
- Clauses requiring unilateral vacatur of the marital home, prohibiting any future modification, or shifting asymmetrical business debt risk to the non-owner spouse may be vulnerable as overbroad, contrary to public policy, or otherwise difficult to enforce.
- Any legal conclusion should be tied to the controlling authority relied on by the governing jurisdiction or, if no source is provided, to the mainstream doctrine typically applied in private-client practice.
## 4. Analytical scaffolds
1. Identify the parties, the governing-law clause, and any forum or residence-related language first.
2. Compare each party’s disclosure side by side:
- what was disclosed,
- how it was valued,
- what documentation backed the value,
- whether the non-owner could independently verify it.
3. For each asset or liability category, ask whether the disclosure is merely self-asserted or is supported by objective evidence.
4. For any business interest, test whether the valuation method is transparent enough for the other party to assess risk and whether the supporting record makes the value credible.
5. For each maintenance or support term, identify whether it is a complete waiver, a partial waiver, or a conditional allocation, then assess whether a limiting feature should be added.
6. Review every clause that allocates post-marital risk, restricts residence, forbids modification, or attempts to foreclose court involvement; assess enforceability under the governing law.
7. For each issue, close the analysis with:
- a scale or magnitude indicator drawn from the source materials when available,
- the interacting clause or related document that changes the risk,
- the practical consequence for the client.
8. Separate non-objectionable provisions from provisions that should be retained with only stylistic or clarifying edits.
## 5. Vertical / structural / temporal relationships
- Start with the governing-law and disclosure picture before turning to individual clauses; those threshold points often determine the seriousness of later issues.
- Treat disclosure issues as front-end execution risks and support-waiver issues as downstream enforcement risks; the timing matters because some standards are assessed at signing and others at enforcement.
- When one clause interacts with another, analyze the combined effect rather than each provision in isolation.
- If multiple jurisdictions or plausible residences are in play, analyze each plausible governing-law path before ranking the issue.
- Place the most serious enforceability and disclosure defects ahead of drafting polish issues, even if the latter are easier to explain.
- Distinguish between provisions likely to be unenforceable as written and provisions that are only overbroad but could be cured by narrowing language.
## 6. Output structure conventions
- Produce a single internal memorandum in conventional legal memo form, not a redline.
- Use a memo header with the parties, the likely governing law or governing-law issue, and a short executive summary.
- Define an ordinal severity scale once at the top and apply it uniformly to every issue entry.
- Organize the body by severity, with each issue entry containing:
- the clause or topic,
- the controlling legal standard,
- a concise analysis,
- the consequence to the client,
- a recommended response.
- For each issue, explicitly identify the relevant authority or doctrine supporting the analysis; do not leave the point as an unsupported conclusion.
- Include a side-by-side disclosure comparison where the source materials permit it.
- Distinguish between problems to strike, problems to narrow, and gaps requiring additional disclosure or verification.
- End with a discrete Recommended Actions section using imperative verbs, assigning the task to the appropriate role and tying it to the transaction timeline or another concrete milestone.
- Keep the tone internal, analytical, and action-oriented; avoid advocacy phrasing directed to the counterparty.
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!