# Draft Defective Industrial Equipment Product Liability

> A case assessment memo for an industrial equipment product liability claim requires analyzing liability theories against the available forensic and workplace-safety findings, evaluating contractual terms-and-conditions defenses, assessing insurance coverage layers, and recommending a venue and early-case strategy.

- Skill: `finchipaiorg/draft-defective-industrial-equipment-product-liability` (Agent Skill)
- Install (CLI): `npx skillmds@latest add finchipaiorg/draft-defective-industrial-equipment-product-liability`
- Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/draft-defective-industrial-equipment-product-liability/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-defective-industrial-equipment-product-liability

---


# Skill: Draft Case Assessment Memorandum for Defective Industrial Equipment Product Liability Claim

## 2. Failure modes the skill is correcting

- Analyzing liability in the abstract without tying each theory to the incident record, forensic mechanism, and any workplace-safety findings that bear on breach, causation, or notice
- Treating design defect, manufacturing defect, and failure-to-warn as interchangeable instead of testing each theory against its own proof structure and defenses
- Missing commercial-contract defenses in the purchase order, warranty language, limitation-of-liability clauses, indemnity provisions, and incorporation language
- Ignoring the interaction between regulatory findings, internal knowledge, and punitive-damages exposure
- Describing damages in aggregate without separating economic loss, personal-injury damages, business interruption or property loss, and any punitive exposure
- Assuming workers’ compensation ends the analysis instead of checking whether the claim is against a third-party manufacturer or other non-employer defendant
- Reviewing insurance at a headline level only, without tracing trigger, limits, layering, exclusions, retention, notice, and defense-cost treatment
- Recommending venue on intuition rather than anchoring it to governing law on damages caps, punitive standards, removal/remand posture, and jury-risk considerations
- Ending with findings but no action plan, or recommendations that do not identify who should do what and by when

## 3. Legal frameworks / domain conventions that apply

- Analyze product liability theories separately: design defect, manufacturing defect, and failure to warn; each turns on different proof and defenses
- Use the governing state’s product-liability standards, including any risk-utility, consumer-expectations, feasible-alternative-design, or statutory defect test that controls the forum
- If the record includes workplace-safety citations or inspection findings, treat them as evidence potentially relevant to industry standards, notice, and negligence, not as automatic liability
- Use forensic engineering findings to establish mechanism of failure, mode of defect, and causation chain; reconcile any mismatch between the expert conclusion and the incident facts
- In commercial equipment sales, analyze UCC warranty rules, disclaimer language, course of dealing, incorporation by reference, and limitation-of-remedy provisions under UCC Articles 2 and 2A as applicable
- Assess contractual indemnity and limitation-of-liability provisions for enforceability between sophisticated commercial parties, including any constraints imposed by public policy or the forum’s commercial-code rules
- Evaluate workers’ compensation exclusivity and third-party product-liability carveouts under the governing state law before discussing who may sue whom
- Assess punitive damages under the controlling state statute or common-law standard, focusing on scienter, conscious disregard, or reckless indifference where the record supports it
- Assess insurance under the governing policy forms: occurrence vs claims-made trigger, products-completed operations, additional insured status if relevant, self-insured retention, per-occurrence and aggregate limits, exclusions, notice, consent, and duty-to-defend rules
- Where venue choices matter, compare the forum’s substantive law on caps, punitive standards, admissibility of regulatory evidence, and procedural posture affecting settlement leverage and trial risk
- For causation and expert issues, rely on the controlling evidence and expert-admissibility standard in the forum, including Daubert v. Merrell Dow Pharmaceuticals, Inc. or the forum’s equivalent

## 4. Analytical scaffolds

- Start with the incident sequence, then map each factual point to the liability element it tends to prove or defeat
- For each liability theory, identify:
  - the governing legal test
  - the evidence supporting it
  - the evidence cutting against it
  - the most likely defense
  - the practical litigation consequence
- Test contractual defenses against the actual purchase documentation, including whether terms were incorporated, accepted, or superseded
- Review internal communications only for legally relevant proof of knowledge, notice, design choices, complaint history, or post-sale conduct
- When punitive exposure is possible, separate conduct evidence from mere outcome evidence and identify the authority that permits or limits punitive recovery
- Quantify damages by category using the source documents, and state whether each category is direct loss, consequential loss, bodily-injury loss, or speculative exposure
- Review the insurance stack in order from primary to excess, and note which layer is likely to respond first, which exclusions may be invoked, and whether defense costs erode limits
- If more than one venue is realistically available, compare them explicitly and recommend the forum that best aligns with the client’s litigation objectives
- End with an action plan that addresses preservation, expert retention, notice, discovery hold, insurer communication, and early dispositive or settlement steps
- When a legal conclusion depends on a rule, statute, regulation, or case, cite the controlling authority by name and section or commonly recognized citation; do not state a conclusion without naming the rule that supports it
- Where the source set contains multiple defendants, multiple policies, multiple incidents, or multiple possible venues, enumerate them first and analyze each separately rather than collapsing them into one composite

## 6. Output structure conventions

- Draft a memo in conventional case-assessment form with headings that naturally cover:
  - Executive Summary and Recommended Strategy
  - Factual Background
  - Liability Analysis
  - Defense Analysis
  - Damages Assessment
  - Insurance and Coverage Analysis
  - Venue Recommendation
  - Immediate Action Plan
- Within the liability section, discuss each theory under its own subheading
- Within the defense section, address contract, causation, comparative fault, exclusivity, and any other record-supported defenses separately
- Within the insurance section, identify the likely responding policy layers and any coverage issues in plain English, then state the practical effect on settlement leverage
- In the venue section, compare the governing law implications before stating a preferred forum
- Conclude with a clear Recommended Actions block that assigns each step to a role or responsible actor and gives an urgency anchor tied to the litigation timeline or a concrete deadline if one appears in the source materials
- Match the requested deliverable filename exactly when provided, and do not substitute a summary or outline for the requested memorandum