# Draft Markup Jda Biopharma Device

> Combined issue log, redline commentary, and strategic cover memo for a joint development agreement in a biopharma-device collaboration, evaluated against client instructions, IP schedule, licensing policy, and prior deal terms.

- Skill: `finchipaiorg/draft-markup-jda-biopharma-device` (Agent Skill)
- Install (CLI): `npx skillmds@latest add finchipaiorg/draft-markup-jda-biopharma-device`
- Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/draft-markup-jda-biopharma-device/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-markup-jda-biopharma-device

---


# Skill: Draft Markup of Joint Development Agreement

## 2. Failure modes the skill is correcting

- Marking up the agreement as if it were a generic collaboration agreement, without integrating the client’s licensing policy, the background-IP schedule, and the prior deal terms into a single comparison set
- Missing deviations from negotiated commercial positions because the draft is read clause-by-clause instead of against the whole source bundle
- Treating joint ownership, field restrictions, sublicensing, and use-rights as standard boilerplate rather than policy-driven terms that may need bespoke overrides
- Overlooking the allocation of regulatory control, data ownership, and development-cost responsibility that is often decisive in a biopharma-device collaboration
- Producing commentary that identifies an issue but does not state severity, explain the clause interaction, or spell out the downstream business, regulatory, or litigation consequence
- Offering only stylistic redlines that are fragile in export, instead of changes that remain intelligible in plain text and can be reviewed line-by-line
- Drafting a memo that summarizes concerns but does not give concrete negotiating direction or operational next steps

## 3. Legal frameworks / domain conventions that apply

- The agreement should be tested against the client’s licensing policy first where policy is more specific than market practice, especially on field-of-use limits, sublicensing, ownership of improvements, and permitted downstream use
- The prior deal term sheet functions as the negotiated commercial benchmark; departures from it should be identified, explained, and, if material, treated as active negotiation points
- Background IP must be ring-fenced with precision so that each party’s pre-existing technology, know-how, and platform rights are excluded from joint ownership except to the extent expressly licensed
- Joint development in a regulated product context should allocate control over regulatory strategy, submissions, data use, adverse-event reporting support, and related costs
- Default rules on joint ownership may not match the parties’ intended exploitation model; the draft should confirm whether the agreement overrides default co-ownership consequences under the governing law
- Clinical, technical, and regulatory data rights should be allocated expressly, because use of those materials often determines both approval strategy and post-development commercialization
- Where the source documents identify governing law, statutory authority, regulatory regime, or policy language, the commentary should anchor conclusions to that authority rather than to abstract market custom

## 4. Analytical scaffolds

- Source-set reconciliation:
  1. client instructions
  2. background-IP schedule
  3. licensing policy
  4. prior deal / term sheet
  5. current draft JDA
  Compare each operative provision against this full set before drafting a change
- Policy-first IP review:
  - background IP
  - foreground / project IP
  - improvements
  - joint inventions
  - license scope
  - sublicensing
  - exclusivity or field restrictions
  - post-termination rights
- Regulatory and development control review:
  - who owns the development plan
  - who controls filings and submissions
  - who bears costs
  - who controls data, reports, and communications with regulators
- Deviation analysis:
  - identify where the draft departs from prior deal economics or allocation of rights
  - state whether the departure is intentional, acceptable with revision, or a negotiation risk
- Issue-log discipline:
  - assign an ordinal severity to each issue
  - tie the issue to the relevant clause and to the source document(s) it conflicts with
  - explain the practical consequence if uncorrected
- Redline discipline:
  - make each substantive edit readable from plain text alone
  - pair each edit with a short rationale comment so the business and legal reason is visible
- Negotiation memo discipline:
  - translate the markup into a concise risk assessment
  - identify must-have positions versus points that can move
  - recommend who should act and what should happen next

## 5. Vertical / structural / temporal relationships

- If the source materials involve more than one party, review each party’s rights, obligations, and asymmetries separately before drafting any joint allocation
- If the draft contains multiple schedules or exhibits, cross-check the main agreement against each schedule to ensure definitions, ownership, and licensing terms are consistent
- If the agreement contemplates phased development, clinical testing, validation, regulatory filing, and commercialization, confirm that rights and controls shift coherently across stages rather than remaining fixed by default
- If the draft addresses pre-signing conduct, in-term development, and post-termination exploitation, treat those as distinct temporal buckets and test each bucket for survivability and residual rights
- If the collaboration spans both product and data rights, keep the vertical relationship clear: technical work may generate data, data may support filings, and filings may drive commercialization rights

## 6. Output structure conventions

- Produce one combined working document that contains:
  1. a severity-ranked issue log
  2. the redlined agreement with inline plain-text change markers and short rationale comments
  3. a strategic cover memo
- Use a defined severity scale at the start of the issue log and apply it consistently to every entry
- For each issue-log entry, include:
  - clause / topic
  - severity
  - source conflict or deviation
  - proposed fix
  - consequence if not fixed
- For each substantive redline, make the change explicit in text using a robust convention that survives export, and include a brief rationale immediately nearby
- The cover memo should state overall risk posture, non-negotiable positions, negotiable items, and the preferred bargaining sequence
- End with a Recommended Actions section that assigns an action, a responsible role, and a timing anchor tied to the drafting or negotiation milestone
- Cite controlling legal authority or policy authority whenever a legal conclusion depends on a rule, statute, regulation, or defined policy requirement
- Keep the writing operative: every section should advance the markup, not merely describe the exercise