Draft Motion To Dismiss Brief

---
name: draft-motion-to-dismiss-brief
task_id: litigation-dispute-resolution/draft-motion-to-dismiss-brief
description: Drafting a Rule 12(b)(6) motion to dismiss brief in a commercial software licensing dispute requires arguing each count's facial legal deficiency based on the complaint's allegations and any documents incorporated by reference or integral to the complaint, and preparing the separate companion deliverables required by the task instructions.
activates_for: [planner, solver, checker]
---

# Skill: Draft Rule 12(b)(6) Motion to Dismiss Brief — Commercial Software Licensing Dispute

## 1. Subject-matter triage

- Confirm the pleading posture: amended complaint, all counts targeted, and the motion is directed to dismissal under Rule 12(b)(6), not summary judgment.
- Identify every source the court may properly consider at the pleading stage: the complaint, exhibits attached to it, documents incorporated by reference, and documents integral to the complaint.
- Treat the requested outputs as separate deliverables; draft the motion first, then the proposed order, then the internal memo.

## 2. Failure modes the skill is correcting

- Using outside facts or dispute narrative not pleaded in the complaint or properly considered at the motion-to-dismiss stage.
- Collapsing distinct counts into one generalized attack instead of testing each count against its own elements and allegations.
- Missing threshold practice requirements that control whether the motion is properly filed, such as formatting rules, filing prerequisites, or local motion procedures.
- Ignoring contract text or attached documents that can defeat, narrow, or cabin the pleaded claims.
- Failing to produce the companion order and internal memo as distinct, usable documents.
- Stating legal conclusions without tying them to the controlling rule, statute, or case authority.
- Writing the memo as a retread of the motion instead of a prioritization tool that surfaces the strongest threshold issues.

## 3. Legal frameworks / domain conventions that apply

- Rule 12(b)(6) and the Rule 8 plausibility standard: the complaint must plead enough factual matter to make relief plausible, not merely possible.
- Twombly and Iqbal: labels, conclusions, and formulaic recitations of elements do not suffice; the court may use judicial experience and common sense.
- Rule 9(b): fraud-based, misrepresentation-based, and similar heightened-pleading claims must be alleged with particularity as to the circumstances.
- Incorporation-by-reference and integral-document doctrine: documents the complaint relies on may be considered without converting the motion into one for summary judgment.
- Contract interpretation principles: integration clauses, limitation-of-liability provisions, disclaimers, notice-and-cure language, and damages exclusions may defeat or narrow pleaded theories when the governing text is properly before the court.
- Commercial software licensing conventions: claims often turn on the license scope, implementation obligations, acceptance criteria, service levels, and allocation-of-risk language rather than broad equity arguments.
- Any consumer-protection or statutory claim must be checked against its threshold predicates, including standing, covered-status prerequisites, notice requirements, and statutory elements.
- If the complaint pleads multiple theories arising from the same commercial relationship, each theory should be tested independently rather than assumed to rise or fall together.

## 4. Analytical scaffolds

- Start with the procedural frame: identify the governing rule, the court’s local motion requirements, and any deadlines or pre-filing conditions that affect the filing posture.
- Then enumerate each count in the amended complaint and list its elements before drafting the argument.
- For each count, ask in sequence:
  - What exact legal theory is pleaded?
  - Which allegations are offered for each element?
  - Which allegations are conclusory, speculative, or unsupported?
  - Which incorporated documents or integral agreements cut against the claim?
  - Which authority governs the pleading standard for that theory?
- If a claim sounds in fraud, misrepresentation, concealment, or statutory deception, apply the heightened pleading standard before addressing the merits.
- If a claim depends on contract language, anchor the analysis in the operative text and address interpretation, integration, disclaimers, damages limitations, and conditions precedent.
- If dismissal may be partial, state precisely whether the defect affects the whole count, particular remedies, or only certain allegations.
- If amendment would be futile as to a theory, explain why in a way tied to the pleaded facts and governing law.
- For the internal memo, lead with threshold issues that may dispose of the case early, then move to secondary defenses and litigation posture.
- When more than one count, document, or threshold condition is in play, analyze them one by one rather than in aggregate; if only one is truly in scope, say so expressly and explain why.

## 5. Vertical / structural / temporal relationships

- In contract-based disputes, distinguish pre-contract representations from written license terms, and distinguish execution-stage promises from post-signature performance disputes.
- Distinguish the original agreement from amendments, order forms, statements of work, change orders, and renewal documents, because later documents may modify earlier obligations or cure alleged gaps.
- Separate allegations about the sale or licensing of software from allegations about implementation, support, maintenance, upgrades, or data issues, since different duties and defenses may govern each period.
- Distinguish liability theories from damages theories; a count can fail as to recovery even if some misconduct is plausibly alleged.
- If a claim depends on notice, cure, exhaustion, or other temporal predicates, test whether the complaint pleads those steps in the required sequence.
- If multiple actors or entities appear in the complaint, keep their roles distinct and do not attribute one entity’s conduct to another without pleaded support.

## 6. Output structure conventions

- Motion to dismiss brief: title, introduction, governing standard, count-by-count argument, and conclusion.
- Use a separate section for each count, with the claim identified by name, the governing authority cited, and the pleaded deficiency stated concretely.
- Where a contractual provision matters, identify the provision and explain how it defeats or limits the pleaded theory.
- Support every legal proposition with controlling authority by name and, where appropriate, rule, section, or case citation.
- Proposed order: concise, court-ready, and specific as to which counts are dismissed and whether dismissal is with or without prejudice.
- Cover memo: internal-only, threshold-focused, and written to identify the strongest dismissal points, litigation risk, and recommended sequencing.
- The memo should end with an explicit recommended-actions section that assigns each step to a role and ties it to the filing timeline or next procedural milestone.
- Keep each deliverable internally complete; do not rely on cross-references that force the reader to consult another draft to understand the requested relief.
- Name the output files exactly as instructed: motion-to-dismiss.docx, proposed-order.docx, and cover-memo.docx.