Draft Answer To Breach Of Contract Complaint

---
name: draft-answer-to-breach-of-contract-complaint
task_id: litigation-dispute-resolution/draft-answer-to-breach-of-contract-complaint
description: Drafting an answer to a breach-of-contract complaint requires responding paragraph-by-paragraph using the available responses (admit, deny, or lack knowledge), pleading affirmative defenses with sufficient factual support, and preserving any viable counterclaims.
activates_for: [planner, solver, checker]
---

# Skill: Draft Answer with Affirmative Defenses to Breach of Contract Complaint

## 2. Failure modes the skill is correcting

- Using blanket denials or generic admissions instead of answering each numbered allegation individually, which can create unintended admissions or weaken later defenses
- Pleading affirmative defenses as labels only, without the underlying factual predicates needed to survive challenge
- Missing defenses that arise from the contract text, performance history, notice sequence, or incorporated documents
- Overlooking counterclaims or setoff theories arising from the same transaction or occurrence
- Failing to align denials and defenses with the governing pleading rule, which can make the answer vulnerable as conclusory or nonresponsive

## 3. Legal frameworks / domain conventions that apply

- Apply the governing rule for answers: respond to each allegation by admitting, denying, or stating that sufficient information is unavailable to form a belief, and deny only what is fairly put in issue
- Apply the governing rule for affirmative defenses: plead them expressly and include enough factual detail to show a plausible basis for each defense
- Apply the governing pleading standard for defenses and counterclaims in the relevant forum, including any requirement that defenses not be asserted as bare conclusions
- Apply contract interpretation rules to the agreement, amendments, notices, exhibits, and related documents that bear on performance, breach, and remedies
- Common contract defenses to evaluate include failure of condition precedent, prior material breach, waiver, estoppel, excuse or impossibility, accord and satisfaction, release, payment, setoff, statute of limitations, and contractual limitations on remedies or damages
- Force majeure and similar excuse provisions must be read according to their text, including triggering event, causation, notice, mitigation, and scope of excuse
- Notice, cure, and termination provisions often operate as contractual prerequisites to relief and should be analyzed before pleading breach or default
- Any counterclaim that may be compulsory under the governing procedural rule should be preserved in the answer or otherwise risk forfeiture

## 4. Analytical scaffolds

- Read the complaint paragraph-by-paragraph and assign a response to each numbered paragraph: admit, deny, or lack sufficient information to admit or deny
- Read the full document set, including the contract and any exhibits, to test whether each allegation is supported, contradicted, qualified, or dependent on a missing condition
- For each denial, ensure it tracks the substance of the allegation rather than merely its wording
- For each affirmative defense, identify the factual basis in the source documents and connect it to the legal theory that makes the defense available
- Separate defenses that defeat liability from defenses that limit remedies, damages, or timing
- Identify any document-driven defenses tied to notice, cure, payment, approval, inspection, acceptance, or waiver language
- Consider whether any claim arising from the same transaction should be pleaded as a counterclaim, recoupment, or setoff, and preserve it if the procedural posture requires
- Keep the answer internally consistent: denials, defenses, and counterclaims should not conflict with each other or concede elements unintentionally
- If the governing law, contract, or instructions identify a specific authority for a defense or procedural rule, cite that authority by name and section or rule in the pleading or drafting notes as appropriate

## 5. Vertical / structural / temporal relationships

- Map the timeline of performance, notice, cure, payment, termination, and breach against the contract’s sequencing requirements
- Treat conditions precedent, notice requirements, and cure periods as threshold issues before merits defenses
- If the complaint depends on a prior notice, demand, or default declaration, test whether the required sequence occurred and whether the timing was contractually sufficient
- If the contract contains remedy limitations, place those defenses alongside liability defenses only where they affect the pleaded claim; otherwise separate them under damages or relief
- If multiple agreements, amendments, change orders, or incorporated documents govern different phases of the relationship, reconcile them before drafting responses

## 6. Output structure conventions

- Use a formal pleading caption and case heading consistent with the forum and the attached complaint
- Include introductory response language that states the defendant answers the complaint and preserves all available defenses
- Provide numbered responses that mirror the complaint’s paragraph numbering and use clear admit/deny/lack-knowledge phrasing
- Include separately numbered affirmative defenses with concise factual support for each defense
- Add counterclaims only if supported by the record and procedurally appropriate
- Include a jury demand if the forum permits it and the client intends to preserve that right
- Draft the operative answer as the primary deliverable and ensure it is complete and non-empty before considering any supplemental notes or summaries
- Follow the formatting requirements of the governing court rules and the task instructions, using industry-conventional pleading structure rather than checklist-style headings