# Draft Joint Development Agreement > Joint development agreement for a collaboration involving co-developed technology, with drafting guidance that protects each party's pre-existing IP and commercialization interests and includes a memo identifying open issues for client decision. - Skill: `finchipaiorg/draft-joint-development-agreement` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/draft-joint-development-agreement` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/draft-joint-development-agreement/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-joint-development-agreement --- # Skill: Draft Joint Development Agreement ## 1. Subject-matter triage - Treat the agreement as a transactional drafting task with a primary contract and a secondary drafting memorandum. - Draft the agreement first; do not let the memo substitute for operative contractual language. - If the source set contains multiple term sheets, exhibits, IP schedules, or commercial variants, enumerate them up front and draft against the governing set rather than blending them. - Confirm the collaboration scope, the technology stack, the development workstreams, and any existing business or licensing constraints before writing ownership and commercialization terms. ## 2. Failure modes the skill is correcting - Drafting background IP provisions without precisely defining which party’s pre-existing technology and know-how is ring-fenced, causing the other side to capture core assets by accident. - Assuming jointly developed IP can be co-owned without addressing exploitation rights, consent mechanics, or default co-owner rules. - Copying commercial economics or milestone mechanics from a term sheet without checking that defined dates, triggers, and payment mechanics actually align. - Leaving exclusivity, field restrictions, and third-party license constraints inconsistent with the intended commercialization model. - Omitting post-termination IP treatment, which leaves the parties without a clear answer on continuing use, license scope, or survivability of development rights. - Failing to produce a drafting memorandum that surfaces open issues, judgment calls, and client decisions that must be made before execution. ## 3. Legal frameworks / domain conventions that apply - Background IP must be defined narrowly and by reference to pre-existing patents, applications, copyrightable works, trade secrets, software, data, designs, and know-how so that each party retains what it brings into the collaboration. - Foreground IP ownership should be chosen deliberately: sole ownership by inventor/developer, joint ownership with tailored use rights, or ownership by one party with a license back to the other. - If joint ownership is used, the agreement should override or manage default co-owner exploitation rules by specifying consent rights, licensing authority, enforcement control, and prosecution strategy. - Commercialization rights should be aligned with field-of-use, territory, channel, exclusivity, and any existing third-party commitments. - Cost sharing and milestone mechanics should be internally consistent, objective, and tied to verifiable deliverables or project phases. - Term, termination, and post-termination provisions should specify what survives, who may continue using what, and whether any post-termination license is exclusive, non-exclusive, perpetual, time-limited, or conditional. - Confidentiality, publication, invention disclosure, patent filing, and data rights should be coordinated so the development program does not undercut later ownership or filing positions. - Governing-law and dispute-resolution choices should be checked against the intended IP enforcement and commercialization posture. ## 4. Analytical scaffolds - Background IP schedule review: identify each party’s pre-existing assets, reserve them expressly, and ensure the definition does not sweep in independently developed improvements unless intended. - Foreground IP architecture: choose an ownership model that matches the client’s commercialization strategy, then draft the operational consequences of that model, including use, assignment, licensing, and enforcement. - Exploitation control: if the parties share rights, decide who may license, who prosecutes, who enforces, who bears costs, and whether consent is required for each action. - Commercial field analysis: map each contemplated product, customer segment, geography, and channel to the applicable rights grant or restriction. - Economics and milestones: verify that each payment trigger corresponds to a defined event, deliverable, or acceptance criterion and that the economic structure is coherent across the document set. - Termination analysis: test what happens on termination, expiration, breach, or project abandonment, including return/destruction of materials and continuing licenses. - Memo issue-spotting: identify open business questions, drafting judgments, and risk tradeoffs that should be escalated to the client rather than silently resolved. ## 5. Vertical / structural / temporal relationships - Structure the agreement to move from scope and definitions to IP ownership, then commercialization, then governance, then economics, then term and exit mechanics. - Keep the relationship between background IP, improvements, and foreground IP explicit at every stage so later provisions do not silently broaden earlier ones. - Tie temporal concepts to the project lifecycle: pre-project materials, during-project creation, acceptance or milestone completion, termination, and post-termination use. - Where rights change over time, state the trigger, the duration, and any end-date or survival period in the same provision. - Make sure any continuing license or use right after termination is consistent with the stated ownership model and with confidentiality and return obligations. ## 6. Output structure conventions - Primary deliverable: a complete joint development agreement with operative provisions, not an outline or commentary. - Include, at minimum, coherent sections for: definitions, scope, background IP, foreground IP, ownership and licenses, development obligations, governance, confidentiality, publication, costs and milestones, warranties or disclaimers as appropriate, term and termination, post-termination rights, dispute resolution, and standard legal boilerplate. - Draft the agreement in commercially conventional contract form, using precise operative language and avoiding placeholders except where the source materials leave a point genuinely open. - Secondary deliverable: a drafting memorandum that identifies open issues, explains key drafting judgments, and recommends positions for unresolved points. - In the memorandum, organize issues in a clear sequence from ownership and scope through commercialization, economics, and exit. - For each open issue, state the practical consequence for the client and the decision needed to finalize the draft. - End the memorandum with a Recommended Actions block that assigns each follow-up to a role and a timing anchor tied to signing, final markup, or business approval. - Before stopping, confirm that the agreement file and the memorandum file each exist, are non-empty, and contain operative drafting rather than a summary of what should be drafted.