patent-workaround

Pressure-test U.S. utility patent claims against credible design-around alternatives using adversarial subagents.

391|46|Updated Aug 12, 2026
One-click install
npx skills add https://github.com/gfodor/legal-skills --skill patent-workaround-gfodor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: patent-workaround
Source: https://github.com/gfodor/legal-skills/tree/main/patent-workaround
Command: npx skills add https://github.com/gfodor/legal-skills --skill patent-workaround-gfodor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Drafting a patent that competitors cannot easily design around is expensive and error-prone. This Skill runs a structured adversarial loop that attacks a draft or pending U.S. utility patent with fresh competitor subagents, then adjudicates each proposed workaround against claim scope, invention umbrella, disclosure support, and prior art before any amendment is made. ## Core Features & Use Cases - Adversarial design-around testing: Fresh subagents act as competitor product architects, systematically mutating claim limitations to find credible workarounds that preserve the invention's value proposition. - Version-locked state tracking: The coverage_state.py script hashes challenge packets, binds adversary reports and adjudications to exact versions, and blocks promotion until two qualifying fresh-adversary cycles complete. - Gated amendment workflow: Every proposed claim or disclosure change passes new-matter, written-description, enablement, prior-art, eligibility, definiteness, and prosecution-risk gates before integration. - Use Case: An inventor with a pre-filing draft runs the skill to discover that a competitor could swap a claimed server-side process for an edge-device equivalent, then adds a supported independent claim and dependent fallbacks covering that mechanism. ## Quick Start Use the patent-workaround skill to adversarially pressure-test my draft utility patent application and identify credible design-arounds before filing.

Frequently Asked Questions about patent-workaround

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test my patent draft against design-arounds before filing?

Run this skill on your draft application: it dispatches fresh competitor subagents to propose credible workarounds, then adjudicates each against claim charts, disclosure support, and prior art. Amendments are only promoted after two qualifying adversary cycles pass all gates.

What is a patent workaround or design-around analysis?

A design-around analysis identifies alternative implementations that deliver the same commercial value while avoiding every limitation of the current claims. The skill classifies each candidate as not-a-workaround, outside-umbrella, umbrella-gap-supported, or umbrella-gap-unsupported.

Does this skill work on pending applications and issued patents?

Yes, but posture matters. Pending applications are checked against the as-filed disclosure with new matter prohibited; issued patents are not rewritten, only flagged for continuation, reissue, or separate-filing questions routed to counsel.

Can this skill replace a patent attorney or give an infringement opinion?

No. It explicitly refuses to issue infringement, noninfringement, validity, patentability, or freedom-to-operate conclusions, and it does not file anything with the USPTO. Outputs are AI-assisted pressure tests requiring review by qualified patent counsel.

Why does the skill require two separate adversary cycles?

The coverage_state.py script enforces an exhaustion rule: promotion of an amended candidate requires qualifying dispositions from two distinct fresh adversaries on the identical packet hash. Any material input change resets the count, preventing premature or stale approvals.