Draft Counterclaim Against Plaintiff For Breach Of Joint Development Agreement

---
name: draft-counterclaim-against-plaintiff-for-breach-of-joint-development-agreement
task_id: litigation-dispute-resolution/draft-counterclaim-against-plaintiff-for-breach-of-joint-development-agreement
description: Drafting a counterclaim for breach of a joint development agreement requires identifying the counterclaims arising from the same transaction, pleading ownership and misuse theories with factual specificity, and coordinating the counterclaim's factual narrative with the defense of the plaintiff's complaint.
activates_for: [planner, solver, checker]
---

# Skill: Draft Counterclaim Against Plaintiff for Breach of Joint Development Agreement

## 1. Subject-matter triage

- Treat the complaint, JDA, NDA, expert materials, emails, access logs, and strategy memo as one integrated source set.
- Identify which claims must be asserted as counterclaims because they arise from the same transaction or occurrence, and separate them from any permissive claims that stand independently.
- Map each asserted theory to the governing agreement, the alleged conduct, and the relief sought before drafting.
- If the source set supports multiple breaches, theories, or time periods, enumerate them first and draft each as a distinct pleaded theory rather than collapsing them into a single narrative.
- Draft the counterclaim as an operative pleading, not a litigation summary.

## 2. Failure modes the skill is correcting

- Pleading ownership, contribution, confidentiality, or misuse in conclusory terms without the underlying facts that show who owned what and how it was used.
- Missing the document trail that ties alleged misuse to particular dates, systems, communications, or access events.
- Failing to distinguish breach of contract, misuse of confidential information, trade secret-type misuse, fraud-based theories, and equitable fallback theories.
- Asserting alternative theories without making the alternatives explicit.
- Omitting allegations that support ongoing harm, irreparable injury, or inadequacy of money damages where injunctive relief is sought.
- Failing to align the counterclaim narrative with the defense to the complaint, which creates internal inconsistency or waiver risk.
- Stating legal conclusions without naming the rule, statute, or doctrine that supports them.

## 3. Legal frameworks / domain conventions that apply

- Rule 13(a) of the Federal Rules of Civil Procedure: compulsory counterclaims arising from the same transaction or occurrence should be identified and, where appropriate, pleaded to avoid waiver.
- Rule 13(b) of the Federal Rules of Civil Procedure: permissive counterclaims may be pleaded if independently viable and jurisdictionally supported.
- Rule 8(a) of the Federal Rules of Civil Procedure: plead a plausible claim with a short and plain statement showing entitlement to relief.
- Rule 9(b) of the Federal Rules of Civil Procedure: fraud-based claims must plead the who, what, when, where, and how with particularity.
- Rule 11 of the Federal Rules of Civil Procedure: factual and legal contentions must have evidentiary support or a nonfrivolous basis for extension or modification.
- Rule 54 and governing state law: prayer for relief should track available damages, equitable remedies, fees, and costs.
- Contract principles governing joint development agreements: ownership, use restrictions, license-back provisions, confidentiality, publication, return/destruction, and termination provisions often control the breach theories.
- NDA principles: confidentiality obligations may create an independent breach theory and may support parallel misuse allegations.
- Trade-secret and confidential-information frameworks, where implicated, should be tied to the actual definition of protected material and the actual use alleged.
- Fraudulent inducement doctrines, where supported by the documents, require a specific misrepresentation theory and a pleading posture consistent with Rule 9(b).
- Unjust enrichment or quantum meruit may be pleaded in the alternative when contract coverage is disputed or unavailable; make the alternative posture explicit.

## 4. Analytical scaffolds

- Read the governing agreements as a whole to identify each party’s promises, ownership allocations, restrictions, notice provisions, and remedies.
- Build a chronology that starts with formation and contribution, then tracks access, disclosures, use, commercialization, or other alleged misuse, and ends with the harm.
- Anchor each factual allegation to a source document whenever possible: agreement text, email, log entry, expert observation, or contemporaneous memo.
- For each claim, state the elements first, then plead the facts that satisfy each element.
- For each alleged breach, specify the obligation, the act or omission, the actor, the timing, and the resulting harm.
- Where access logs or emails evidence misuse, identify the system, the date range, the nature of access, and how that access conflicts with the agreement.
- Where expert material is used, tie the opinion to the factual record rather than reciting conclusions.
- Where fraud is alleged, plead the specific statement or omission, who made it, when and where it was made, why it was false, and how it induced the agreement or performance.
- Where damages are not fully measurable or the harm is continuing, plead facts supporting injunctive relief in addition to monetary relief.
- If multiple theories cover the same conduct, preserve them as alternative counts and avoid accidental election of remedies.
- Check that the counterclaim does not contradict the answer narrative on ownership, authorization, or reliance.

## 5. Vertical / structural / temporal relationships

- The timeline should connect agreement execution, contribution of materials or know-how, access to project data, alleged misuse, notice, and resulting damage in that order unless the source set shows a different sequence.
- Confidentiality obligations, retention obligations, and use restrictions must be matched to the period in which the challenged conduct occurred.
- Ownership provisions set the baseline rights; later conduct is analyzed against that baseline, not in isolation.
- If the source set contains multiple disclosures or use events, distinguish them by date, channel, and subject matter so the pleading reflects a real sequence rather than a single generalized accusation.
- If the relief sought depends on continuing conduct, the narrative should show why the conduct is ongoing or likely to recur.

## 6. Output structure conventions

- Use a court-ready caption naming the plaintiff as counterdefendant and the defendant as counterclaimant.
- Include an introductory paragraph that identifies the governing relationship and the basis for counterclaim jurisdiction, if appropriate.
- Present a concise factual background that integrates the agreement terms with the documentary evidence.
- Plead each count separately with a clear title, the governing legal theory, and factual allegations matched to the elements.
- Label alternative theories as alternative where they depend on the same nucleus of facts.
- Include a prayer for relief that tracks the asserted theories and available remedies, including damages, disgorgement or restitution if supported, injunctive relief if ongoing harm is alleged, fees where authorized, and costs.
- Include a jury demand only if the forum and claims support one.
- Keep the filing format consistent with the applicable forum’s pleading conventions and the task instructions.