← ClaudeAtlas

recipe-infringement-chartinglisted

Litigation recipe for an element-by-element infringement claim chart — verify the patent is in force where it matters, decompose the asserted claims, extract accused-product evidence (OCR datasheets and manuals), and map every element with literal and doctrine-of-equivalents columns. Trigger when the user asks whether a product infringes a patent, wants a claim chart, or needs element-by-element infringement mapping.
flowleap-ai/flowleap-plugins · ★ 0 · Data & Documents · score 75
Install: claude install-skill flowleap-ai/flowleap-plugins
# Recipe: Infringement Charting Map asserted claims onto an accused product, element by element. ## Step 1: Asserted Patent Intake ```bash flowleap --json summary <asserted-patent> # biblio, legal status, family, term flowleap --json ops claims <asserted-patent> flowleap --json ops description <asserted-patent> # claim-construction support ``` ## Step 2: Enforceability Check A chart against an expired or lapsed patent is wasted work — check first: ```bash flowleap --json ops legal <asserted-patent> # status events flowleap --json tools run get_patent_term patent_number=<asserted-patent> # expiry estimate flowleap --json ops family <asserted-patent> # where it is in force ``` Only chart in jurisdictions with a live family member. ## Step 3: Decompose the Asserted Claims Save each asserted independent claim to a file, then: ```bash flowleap analyze-claim --file claim1.txt --focus elements ``` The element list becomes the chart's rows. Every element must be met — one missing element defeats literal infringement of that claim. ## Step 4: Accused-Product Evidence Intake ```bash flowleap ocr ./accused-product-datasheet.pdf > datasheet.md flowleap ocr https://example.com/product-manual.pdf > manual.md ``` Collect: datasheets, manuals, teardown reports, marketing claims. Note the provenance of every document — the chart cites evidence, not impressions. ## Step 5: Build the Chart | Claim element | Claim