# Draft Ip Assignment Series A

> Execution-ready founder IP assignment agreement and cover memo for a startup financing transaction, addressing material IP risks and pre-closing action items identified in diligence.

- Skill: `finchipaiorg/draft-ip-assignment-series-a` (Agent Skill)
- Install (CLI): `npx skillmds@latest add finchipaiorg/draft-ip-assignment-series-a`
- Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/draft-ip-assignment-series-a/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: FinchipAIOrg (https://skillmd.com/u/finchipaiorg)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/finchipaiorg/draft-ip-assignment-series-a

---


# Skill: Draft Intellectual Property Assignment Agreement — Startup Founder IP Assignment

## 1. Subject-matter triage

- Treat the assignment agreement as the primary deliverable; draft it first, then prepare the cover memo only after the agreement is complete and internally consistent.
- Confirm the source set identifies each founder, each relevant IP bucket, and any prior obligations before drafting; if the diligence record is incomplete, surface the gap rather than guessing.
- Separate assigned company IP from clearly personal IP, but draft the transfer language broadly enough to capture all business-related inventions, code, writings, data, documentation, trade secrets, and related rights.

## 2. Failure modes the skill is correcting

- Drafting a generic founder IP assignment that ignores founder-specific diligence findings, especially prior employer restrictions, academic research obligations, moonlighting clauses, or joint-development history.
- Omitting founder-by-founder representations and disclosure schedules that make the chain of title credible for financing.
- Failing to connect the agreement to the company’s investor-facing IP reps and thereby leaving a gap between internal cleanup and closing deliverables.
- Writing a memo that merely summarizes risks instead of identifying concrete pre-closing cures, responsible parties, and timing.
- Treating all founders as interchangeable when their employment history, research affiliations, and prior invention assignments differ.
- Leaving ambiguity around pre-formation work, side projects, open-source contributions, invention notebooks, source code repositories, and other preexisting assets that the company has been using.

## 3. Legal frameworks / domain conventions that apply

- Use startup financing chain-of-title conventions: the company should receive all right, title, and interest in founder-created IP that is intended for the business, including pre-incorporation work and derivative work built into the product.
- Address prior employer invention-assignment and confidentiality covenants by representation, disclosure, and specific exception handling where the source documents indicate possible overlap.
- Address university or research-institution claims by requiring disclosure of affiliations, sponsored research, lab use, grant conditions, and any waiver or release needed to clear ownership.
- Address joint authorship or co-invention risk by obtaining written assignments from all contributors or expressly carving out third-party rights if the source record shows non-founder involvement.
- Align drafting with the usual financing package: assignment agreement, disclosure schedules, and a cover memo that explains residual risk and whether closing can proceed on a clean or conditional basis.
- Support every legal conclusion with the governing source of authority available in the record or a generally recognized doctrine of assignment, invention ownership, confidentiality, or work-made-for-hire as applicable.

## 4. Analytical scaffolds

- Analyze founder by founder, then asset by asset: for each founder, map employment history, prior agreements, academic affiliations, consulting or moonlighting, and known contributions to the company.
- For each issue, identify the affected IP category, the source of the restriction, the likely ownership or use claim, and the drafting response.
- Distinguish between ownership risk, use restriction risk, disclosure risk, and closing-condition risk; do not collapse them into a single generic concern.
- Draft representations to match the actual risk profile: if a founder has no identified external claims, state that cleanly; if there is a flagged relationship, narrow the rep and add a disclosure-based exception or required deliverable.
- Build the agreement around operative transfer language plus schedules for:
  - assigned IP categories,
  - excluded preexisting property, if any,
  - prior obligations and disclosures,
  - required post-signing or pre-closing cleanup.
- In the cover memo, organize discussion by founder, then by risk type, then by required action and closing implication.
- If the source record presents multiple founders, multiple projects, or multiple jurisdictions, enumerate them before analysis and apply the same review logic to each item without assuming identical outcomes.

## 5. Vertical / structural / temporal relationships

- Track the timeline of each founder’s activity: pre-incorporation development, employment periods, university tenure, consulting windows, post-formation assignments, and any date when company work began.
- Tie each risk to the relevant transaction stage: draft-time disclosure, signing-time assignment, pre-closing cure, or closing-condition satisfaction.
- Where the source materials show overlapping roles or concurrent affiliations, analyze how those overlaps affect ownership, confidentiality, and the ability to make investor reps at closing.
- If an issue turns on earlier work later incorporated into the product, capture both the original creation date and the later integration date so the assignment language covers the full chain.
- Use temporal sequencing to decide whether a waiver, release, consent, re-signing, or supplemental assignment is needed before closing.

## 6. Output structure conventions

- Draft `ip-assignment-agreement.docx` as an execution-ready agreement, not a memo about an agreement.
- Include:
  - title and parties,
  - recitals tied to the financing context,
  - assignment grant with full transfer language,
  - founder representations and covenants tailored to identified risks,
  - disclosure or exception schedule references,
  - further assurances and cooperation,
  - governing law and execution blocks,
  - schedules for IP categories and founder-specific prior obligations.
- Draft `ip-assignment-cover-memo.docx` as a concise advisory memo that:
  - identifies each material IP risk by founder,
  - explains the drafting response chosen,
  - states what must be done before closing,
  - flags any residual risk for investor-facing IP representations,
  - ends with a Recommended Actions section naming the responsible role and the timing trigger.
- Use conventional legal drafting language, but do not substitute boilerplate for source-specific analysis.
- Where the source documents support a proposition, cite the controlling authority or operative document basis in the memo rather than asserting the conclusion bare.
- Before finishing, verify that the agreement file is complete and operative, and that the memo follows only after the agreement exists.