complaint-breach-of-contract
Drafts a U.S. plaintiff-side breach of contract complaint with caption, jurisdiction/venue, four-element cause of action, and prayer for relief. Trigger when user needs to draft a breach of contract complaint for state or federal court filing.
Best use case
complaint-breach-of-contract is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Drafts a U.S. plaintiff-side breach of contract complaint with caption, jurisdiction/venue, four-element cause of action, and prayer for relief. Trigger when user needs to draft a breach of contract complaint for state or federal court filing.
Teams using complaint-breach-of-contract should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/complaint-breach-of-contract/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How complaint-breach-of-contract Compares
| Feature / Agent | complaint-breach-of-contract | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Drafts a U.S. plaintiff-side breach of contract complaint with caption, jurisdiction/venue, four-element cause of action, and prayer for relief. Trigger when user needs to draft a breach of contract complaint for state or federal court filing.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Complaint for Breach of Contract Generates a litigation-ready plaintiff-side complaint structured around the four breach-of-contract elements with jurisdiction-appropriate procedural compliance. ## Prerequisites Collect before drafting: 1. **Governing contract** — executed agreement with amendments, exhibits, attachments 2. **Correspondence** — emails, letters, cure/notice communications (chronological) 3. **Performance evidence** — invoices, delivery records, payment confirmations 4. **Breach evidence** — documentation of defendant's failure, cure notices, responses 5. **Damage calculation** — itemized losses with supporting documentation 6. **Filing court** — jurisdiction, division, and applicable local rules ## Quick Start 1. Identify filing court and confirm jurisdiction (federal diversity/question vs. state general) 2. Extract party details, contract terms, and breach facts from uploaded documents 3. Draft complaint sections in order: caption, jurisdiction/venue, parties, facts, cause of action, relief 4. Verify procedural requirements (jury demand, verification, Rule 11) against local rules ## Complaint Sections ### 1. Caption - Full court name with division/department - Case number (if pre-assigned) - Complete legal names and capacities of all parties - Jurisdiction-specific formatting per local rules ### 2. Jurisdiction & Venue | Element | Federal | State | |---|---|---| | Subject matter | Diversity: 28 U.S.C. § 1332 (complete diversity + AIC > $75K) or federal question: § 1331 | Statutory/constitutional general jurisdiction | | Venue | 28 U.S.C. § 1391: defendant residence, contract performance, or breach location | Defendant residence, place of business, or performance/breach location | State amount in controversy when jurisdictionally required. ### 3. Party Identification - **Individuals**: legal name, address, contractual role - **Entities**: legal form, state of organization, principal place of business, registered agent - **Representative parties**: capacity and source of authority ### 4. Factual Background Chronological narrative covering: - **Formation** — date, place, consideration, essential terms - **Plaintiff's performance** — dates, amounts, deliverables - **Defendant's breach** — obligations unperformed, breach date, cure notice status - **Defendant's response** — acknowledgment, dispute, or silence - **Resulting harm** — causal link from breach to damages Ground all allegations in uploaded documents with specific dates, amounts, and quoted contract language. ### 5. Cause of Action Allege each element with dedicated factual paragraphs: 1. **Valid enforceable contract** — parties, subject matter, consideration, mutual assent; address statute of frauds if applicable 2. **Plaintiff's performance** — conditions precedent satisfied or excused/waived 3. **Defendant's material breach** — provisions violated, manner, date 4. **Resulting damages** — causal link to quantified harm Incorporate contract-specific provisions: notice requirements, cure periods, liquidated damages, attorney's fees clauses. [VERIFY jurisdiction-specific element variations beyond standard four elements] ### 6. Prayer for Relief - Compensatory damages (itemized where calculable) - Consequential/special damages (allege foreseeability at contracting) - Specific performance or injunctive relief (where legally available) - Pre-judgment and post-judgment interest (cite applicable rate/statute) - Costs of suit - Attorney's fees (if contract or statute authorizes) - Punitive damages (only if jurisdiction permits and facts support bad faith) - General relief catch-all ### 7. Procedural Requirements - **Jury demand** — include in body or file separately per local rules - **Rule 11 certification** — good faith factual and legal basis for all allegations - **Verification** — sworn verification if required by state court - **Signature block** — attorney name, bar number, firm, address, phone, email ## Pitfalls & Checks - Number all paragraphs consecutively for cross-reference in motions - Keep factual, objective tone — no inflammatory language; reserve argument for briefs - Ensure factual narrative preemptively addresses likely affirmative defenses: statute of frauds, waiver, impossibility, accord and satisfaction - All allegations must be supportable by documents in counsel's possession at filing - Verify local rules for page limits, margins, font, and spacing before finalizing
Related Skills
managing-privacy-breach-response
Guides HIPAA breach investigation with risk assessment, notification requirements, and remediation documentation. Use when managing data breaches, assessing breach risk, or documenting breach response.
wrongful-termination-complaint
Drafts wrongful termination complaints for employment litigation. Covers at-will exceptions, statutory claims (Title VII, ADA, ADEA, FMLA, state equivalents), public policy violations, and whistleblower protections. Use when drafting or filing a wrongful termination complaint or related employment discharge claim.
third-party-complaint
Drafts a Third-Party Complaint (impleader) under FRCP 14 or state equivalents. Use when a defendant needs to implead a party for indemnification, contribution, subrogation, or breach of warranty during the pleadings phase.
subcontractor-agreement
Drafts enforceable U.S. subcontractor agreements governing general contractor/subcontractor relationships for construction and service projects. Covers scope of work, payment and retainage, insurance and bonding, indemnification, schedule compliance, termination, and dispute resolution with state-specific compliance. Use when drafting subcontracts, subcontractor agreements, construction service agreements, or contractor engagement documents.
subcontracting-plan
Drafts a FAR 52.219-9-compliant Small Business Subcontracting Plan for federal prime contractors. Sets percentage goals for SB, SDB, WOSB, HUBZone, VOSB, and SDVOSB with market-based justifications, outreach strategies, and eSRS reporting. Use when preparing subcontracting plans for federal proposals, responding to FAR 52.219-9, or updating existing subcontracting commitments.
specific-performance-complaint
Drafts a Complaint for Specific Performance compelling contractual fulfillment through equitable relief. Use when filing suit for specific performance, real estate breach, unique property disputes, or equitable remedy pleadings.
retaliation-complaint
Drafts U.S. employment-retaliation complaints with jurisdiction, causation, and remedy sections aligned to the governing statute. Use when counsel needs a filing-ready complaint after a plaintiff alleges adverse action following protected activity. Covers Title VII, FLSA, SOX, and Dodd-Frank retaliation claims, administrative-exhaustion preservation, and prayer-for-relief drafting.
quiet-title-complaint
Drafts a court-ready Complaint to Quiet Title for real property disputes. Guides through intake, chain-of-title verification, adverse claim identification, and strategic pleading. Use when drafting quiet title complaints, clearing title defects, challenging adverse possession, resolving boundary disputes, removing invalid liens, or establishing superior title.
purchase-agreement-breach-complaint
Drafts a U.S. civil complaint for breach of a real estate purchase agreement, covering jurisdiction, venue, parties, contract terms, breach allegations, damages, and remedies including specific performance. Use when preparing a breach of purchase agreement complaint, real estate contract dispute pleading, or specific performance action.
patent-infringement-complaint
Drafts a federal patent infringement complaint for U.S. District Court satisfying FRCP Rules 8, 10, 11 and Twombly/Iqbal plausibility. Covers direct (§ 271(a)), induced (§ 271(b)), and contributory (§ 271(c)) infringement with TC Heartland venue analysis and Halo willfulness. Use when initiating patent infringement litigation, drafting an IP complaint, or preparing a pleading to survive a Rule 12(b)(6) motion.
partition-complaint
Drafts a U.S. civil complaint for partition of real property by co-owners, pleading jurisdiction, ownership interests, property description, encumbrances, and grounds for partition in kind or by sale. Trigger when the user needs a partition action, co-owner dispute complaint, tenant-in-common or joint-tenancy division, or court-ordered sale of real property.
managed-care-contract
Drafts managed care contracts between MCOs and healthcare providers covering payment methodology (FFS/capitation), credentialing, utilization management, HIPAA compliance, quality assurance (HEDIS/CAHPS), termination, indemnification, and dispute resolution. Ensures compliance with Anti-Kickback Statute, Stark Law, CMS MA/Medicaid guidelines, state insurance laws, and NCQA/URAC standards. Use when establishing provider networks, onboarding providers, updating managed care agreements, or negotiating MCO-provider contracts.