Draft Ip Assignment Agreement

---
name: draft-ip-assignment-tech-acquisition
task_id: intellectual-property/draft-ip-assignment-agreement
description: Buyer-protective IP assignment agreement for a technology portfolio acquisition, drafted from diligence materials, asset schedules, and deal terms.
activates_for: [planner, solver, checker]
---

# Skill: Draft IP Assignment Agreement for Technology Acquisition

## 1. Subject-matter triage
- Treat the assignment as a title-transfer document, not a summary of diligence.
- Identify whether the source package includes registered rights, pending applications, unregistered software, source code, trade secrets, domains, data rights, improvements, and related claims; draft to capture each category that is actually in scope.
- If the source materials show multiple sellers, affiliates, or asset holders, map which entity conveys which assets before drafting operative language.
- If any asset is encumbered, licensed, co-owned, or held through an intermediary, resolve that status in the agreement structure before finalizing the assignment clause.

## 2. Failure modes the skill is correcting
- Drafting the assignment too narrowly by listing only enumerated assets, leaving out related rights, proceeds, claims, renewals, continuations, improvements, derivative materials, and ancillary interests.
- Failing to align the transfer language with the diligence record, so that the document says more or less than the assets actually being sold.
- Omitting treatment for outbound licenses, third-party permissions, open-source components, privacy/data constraints, or other use restrictions disclosed in diligence.
- Missing lien releases, payoff mechanics, consent mechanics, or other title-cleanup steps that must occur at or before closing.
- Leaving out cooperation, recordation, prosecution assistance, or further assurances language needed to perfect ownership and maintain chain of title.
- Drafting buyer-favorable covenants and warranties in a way that is not tethered to the actual schedules and disclosures, creating avoidable internal inconsistency.
- Failing to make the document self-executing on closing, with clear conveyance, deliverables, and post-closing obligations.

## 3. Legal frameworks / domain conventions that apply
- Use a broad present assignment of all right, title, and interest in the scheduled assets, plus related rights reasonably necessary to exploit and enforce them.
- Pair the schedule with functional catch-all language so the transfer reaches associated goodwill, causes of action, priority rights, prosecution rights, and derivative or replacement materials where transferable.
- Treat the agreement as a chain-of-title instrument: it should support recordation, office action response, assignment filings, and later enforcement.
- Address encumbrances expressly through release, payoff, consent, or subject-to treatment depending on the deal terms and diligence findings.
- Draft representations and warranties to match the diligence record on ownership, authority, non-infringement, non-encumbrance, open-source use, disclosure of licenses, and absence of undisclosed transfers.
- Include covenants on pre-closing cleanup, post-closing cooperation, and further assurances as standard mechanics for IP transfers.
- Where local law or asset type matters, use the governing authority for assignment formality, recordation, and perfection requirements applicable to the relevant IP class.
- Keep the document consistent with standard transactional drafting conventions: defined terms, schedules, operative assignment, closing deliverables, seller covenants, buyer protections, and signature blocks.

## 4. Analytical scaffolds
- Start from the asset schedule, then draft a conveyance clause that captures both specifically identified assets and all associated rights that follow those assets.
- For each asset class, ask whether title can transfer immediately, whether consent is needed, and whether a separate assignment, recordation, or notice step is required.
- For each disclosed restriction, decide whether the agreement should: assign subject to it, require termination before closing, or require a closing deliverable proving release or consent.
- For each diligence disclosure about software or codebase composition, convert the findings into targeted representations and, where needed, a pre-closing remediation covenant.
- For each encumbrance, draft a corresponding release, payoff, discharge, or covenant to procure the same.
- For each item that requires later action, include a specific further assurances obligation and a cooperation clause tied to post-closing administration.
- If the source materials identify multiple schedules, keep the operative assignment clause global and use the schedules to organize precision, not to limit scope unintentionally.

## 5. Vertical / structural / temporal relationships
- Structure the agreement so the closing transfer happens first, with title and risk allocation fixed at closing and cleanup obligations addressed separately.
- Distinguish among pre-closing obligations, closing deliverables, and post-closing cooperation so the timing of each duty is obvious.
- If third-party consent or release is needed, place it as a condition to closing or a specifically identified closing deliverable, not as an implied hope.
- If the assets include applications or registrable rights, preserve the right to file, amend, prosecute, and renew them after closing.
- If there is a chain of related entities or transferred work product, ensure the conveyance language tracks upstream and downstream ownership so the buyer receives all transferable interests.
- If the agreement interacts with ancillary transaction documents, keep the assignment consistent with the main purchase terms, disclosure schedules, and any IP-specific closing documents.

## 6. Output structure conventions
- Produce a complete buyer-protective IP assignment agreement, not a memo about the agreement.
- Use ordinary contract architecture: recitals, definitions if needed, assignment operative language, representations and warranties, covenants, closing conditions or deliverables, further assurances, governing law, and signature blocks.
- Include schedules for the transferred patent/application assets and other IP assets as needed by the source materials.
- Make the assignment clause broad enough to avoid title gaps, but keep the schedule list accurate and internally consistent with diligence and deal terms.
- Include express treatment of licenses, encumbrances, and open-source or software-related disclosures only to the extent supported by the source record.
- Include cooperation with prosecution, filing, recording, and correction of chain-of-title issues as a distinct post-closing obligation.
- Draft for immediate use in a transaction file: the document should be execution-ready, not a template commentary.