fto-triage

Run freedom-to-operate triage by mapping patent claims to product descriptions.

Updated May 19, 2026
One-click install
npx skills add https://github.com/jrhueiueng/codex-for-legal --skill fto-triage-jrhueiueng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fto-triage
Source: https://github.com/jrhueiueng/codex-for-legal/tree/main/plugins/jrhueiueng/codex-for-legal/skills/ip-legal__fto-triage
Command: npx skills add https://github.com/jrhueiueng/codex-for-legal --skill fto-triage-jrhueiueng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Freedom-to-operate triage helps identify potentially blocking patents early, so legal review can focus on the most plausible risks before a product is launched.

Core Features & Use Cases

  • Structured FTO-style first pass: Runs an intake to capture product/process details, jurisdictions, timing, and known patent signals.
  • Preliminary patent search (when available): Uses connected patent-research integrations (e.g., Solve Intelligence) or limits analysis to user-supplied patents if no database is connected.
  • Claim-chart first pass on the most plausible patents: Builds element-by-element literal read for independent claims and flags doctrine-of-equivalents considerations separately.
  • Open questions + next steps: Produces a triage memo with what a real FTO study would need next (e.g., enforceability, prosecution history, PTAB outcomes, licenses).

Quick Start

Run /ip-legal:fto-triage with a short description of your product and the jurisdictions you plan to launch in.

Frequently Asked Questions about fto-triage

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

FAQPage Schema
How do I run a freedom-to-operate triage to find blocking patents before a product launch?

Freedom-to-operate triage identifies potentially blocking patents by running a guided intake, optionally searching patent corpora, and mapping the most plausible utility-patent claims to your product description. It provides a structured first look at infringement risk without reaching a clearance conclusion.

What is a claim chart first pass and how does it map patent claims to a product?

A claim chart first pass builds an element-by-element literal read for independent claims against a product description, flagging doctrine-of-equivalents considerations separately. This structured mapping highlights potentially blocking patents by showing how product features align with claim limitations.

Can I perform an infringement risk assessment using only user-supplied patents if no patent database is connected?

Yes, you can perform an infringement risk assessment using only user-supplied patents when no database integration is available. The triage maps those specific utility-patent claims against your product description to flag potential blocking risks without requiring an external search.

Does an FTO triage replace the need for formal patent counsel or a legal clearance opinion?

No, an FTO triage does not replace patent counsel or a legal clearance opinion. It includes explicit non-opinion guardrails and safety gating for willfulness, serving only as a structured first pass to focus legal review on the most plausible risks before launch.

What do I need to prepare before starting a patent triage workflow for my product?

Before starting a patent triage workflow, you need a short description of your product, process, or feature, along with the jurisdictions where you plan to launch. This intake information anchors the claim-chart mapping and the assessment of potentially blocking utility patents.

What are the limitations of using an automated FTO triage for early-stage product evaluations?

An automated FTO triage is limited to early-stage and near-launch evaluations, providing a first look at blocking patents without reaching a clearance conclusion. It does not assess enforceability, prosecution history, or PTAB outcomes, and it requires patent counsel for formal legal decisions.