patent-workaround
Adversarially pressure-test a draft or pending U.S. utility patent against technically credible, commercially plausible design-arounds that preserve its value proposition while avoiding the current proposed claims. Use fresh competitor subagents, then have the outer agent decide whether each workaround remains inside the invention's intended umbrella based on the design objectives, motivating problem, disclosed solution, and any deployed implementation; strengthen supported claims or disclosure only after new-matter, written-description, enablement, prior-art, eligibility, definiteness, and prosecution-risk gates. Use for design-around testing, workaround resistance, claim-scope gap analysis, competitive-evasion review, or iterative patent-scope hardening; not as an infringement opinion, freedom-to-operate opinion, patentability guarantee, or substitute for patent counsel.
Install
git clone https://github.com/gfodor/legal-skills /tmp/legal-skills && ln -s /tmp/legal-skills/patent-workaround ~/.claude/skills/patent-workaroundFrom README
Adversarial patent workaround testing Run a version-locked competitor/drafter loop. Keep the main agent in the strategic patent-drafter role and use a fresh subagent as the competitor/product architect for each challenge cycle. The goal is not maximal claim breadth. The goal is supported, patentable coverage of commercially material alternatives that genuinely belong to the invention, with deliberate visibility into what remains outside the claims. Never describe a result as proof of infringement, noninfringement, validity, enforceability, patentability, or freedom to operate. Recommend review by qualified patent counsel before filing or relying on any amendment. Read before acting Read all of these files completely: references/workaround-protocol.md for the adversary's role and output contract. references/integration-gates.md for umbrella classification and amendment gates. references/current-sources.md for the current-law and prior-art source hierarchy.