Draft Markup Of Ip Assignment Agreement

---
name: draft-markup-ip-assignment-buyer
task_id: intellectual-property/draft-markup-of-ip-assignment-agreement
description: Buyer-favorable annotated markup of a seller-drafted intellectual property assignment agreement with bracketed comments explaining each proposed change, informed by due diligence and deal terms.
activates_for: [planner, solver, checker]
---

# Skill: Draft Buyer-Favorable Markup of IP Assignment Agreement

## 1. Subject-matter triage (only if applicable)

- Treat the agreement as a title-transfer document first, not a generic contract: the core question is whether the buyer receives clean, complete, and recordable rights in the assigned IP.
- Review the diligence set and deal documents before marking up the draft so the changes reflect actual ownership, lien, license, and chain-of-title risks rather than abstract preferences.
- If the source set identifies multiple assets, parties, jurisdictions, filings, or encumbrances, enumerate them before drafting so each gets a tailored treatment rather than a one-size-fits-all revision.
- If the draft is missing schedules or exhibits that define the asset package, flag that omission in the markup and make the operative clause broad enough to capture related rights, proceeds, and ancillary claims.

## 2. Failure modes the skill is correcting

- Marking up the seller’s draft without tying the revisions to due diligence findings that require contractual protection through representations, warranties, covenants, or closing conditions.
- Treating title defects, liens, or inconsistent license obligations as background diligence issues instead of converting them into operative closing protections.
- Rewriting the assignment clause in isolation while leaving schedules, definitions, ancillary IP, and post-closing perfection mechanics untouched.
- Failing to mark every substantive change in a way that survives export and review outside tracked-changes view.
- Omitting bracketed commentary on why each change matters in the negotiation, leaving the client without a usable rationale for each position.
- Using vague priority labels or bare assertions instead of a consistent severity signal for the most material issues.
- Offering criticism without a concrete next step for counsel or the business team.

## 3. Legal frameworks / domain conventions that apply

- An IP assignment should transfer all right, title, and interest in the assigned assets, subject only to buyer-accepted exclusions that are expressly identified.
- Ownership and chain-of-title concepts govern whether the seller can transfer what it purports to assign; the draft should track any gaps in invention, authorship, registration, or recordation history.
- Representations and warranties commonly address ownership, authority, non-infringement, absence of conflicting obligations, no known claims, and absence of liens or encumbrances.
- Existing security interests, pledges, or similar encumbrances should be released or terminated at or before closing if the buyer is expected to receive unclouded title.
- Existing outbound licenses, implied rights, or use restrictions must be reconciled with the buyer’s intended ownership and exploitation rights.
- A further assurances covenant should require execution of additional documents needed for recordation, prosecution transition, and perfection of transfer.
- If the source documents allocate specific closing deliverables or survival concepts, the markup should align the assignment agreement with those deal mechanics rather than creating inconsistent timing or remedy provisions.
- Cite the controlling legal authority for each legal proposition used in commentary, whether that authority comes from the source documents or from recognized IP assignment practice.

## 4. Analytical scaffolds

- Assignment scope review: confirm that patents, applications, copyrights, trade secrets, domain-related rights, moral-rights waivers, work product, and related goodwill are covered to the extent contemplated by the deal.
- Due diligence integration: for each identified risk, map the change to the correct mechanism—representation, warranty, covenant, condition precedent, bring-down, closing deliverable, or post-closing undertaking.
- Encumbrance treatment: identify every lien or adverse claim reflected in the source set and require release, termination, or alternative buyer protection before closing.
- License reconciliation: identify every active license or reserved right and determine whether it must be terminated, carved out, disclosed, assumed, or specially preserved.
- Recordation and perfection: strengthen transfer mechanics so the buyer can record assignments and obtain any further documents needed to perfect ownership or defend priority.
- Commentary discipline: each bracketed note should explain the business or legal reason for the change, the negotiation objective, and the consequence if the language remains as drafted.
- Severity assignment: classify each commentary item by a consistent ordinal scale defined once at the top of the markup, and use that scale uniformly throughout.
- Change encoding: mark every substantive addition, deletion, or replacement in text, not just by styling, so the markup remains intelligible in plain text or converted formats.

## 5. Vertical / structural / temporal relationships (only if applicable)

- Track how the assignment clause interacts with the schedules, definitions, disclosure qualifications, closing deliverables, and any post-closing cooperation obligations.
- If the source set distinguishes pre-closing, closing, and post-closing obligations, keep those phases distinct in the markup and do not collapse them into one general promise.
- If certain rights are contingent on third-party consent, release, or notice, place that condition where it affects closing mechanics rather than burying it in commentary.
- Where the draft allocates obligations across buyer, seller, or their affiliates, ensure the markup preserves a clean transfer path and does not leave gaps in responsibility for transition steps.
- If multiple assets or rights are being transferred, address each category in the order that best matches the operative sections of the agreement and the source schedules.

## 6. Output structure conventions

- Produce the buyer-side annotated markup as the primary deliverable; do not substitute a summary for the markup.
- Use robust textual redline conventions that remain visible outside Word formatting, such as explicit deleted, inserted, and replaced text markers, alongside the document’s normal tracked-changes styling if available.
- Attach a short bracketed rationale to each substantive edit so the reader can see the legal or business basis for the proposed change.
- Include a defined severity label with every commentary item, using the same scale throughout the document.
- Organize the markup in the same general order as the agreement, with comments placed near the affected provision rather than in a detached memo.
- When multiple issues are present, keep each issue discrete so the client can accept, reject, or renegotiate them independently.
- End with a concise Recommended Actions block that tells counsel what to verify, what to revise, and what to confirm before signing or closing.
- Before finishing, confirm that the markup file is the operative deliverable, is non-empty, and contains the actual revised language and commentary rather than a description of them.