fto-triage

Map independent claim elements to product features for patent risk triage.

109|20|Updated Mar 7, 2025
One-click install
npx skills add https://github.com/stakwork/stakgraph --skill fto-triage-stakwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fto-triage
Source: https://github.com/stakwork/stakgraph/tree/main/mcp/skills/ip-legal/fto-triage
Command: npx skills add https://github.com/stakwork/stakgraph --skill fto-triage-stakwork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured first look at potentially blocking utility patents without presenting the result as a freedom-to-operate opinion, helping teams identify patent risks before launch and route decisions to qualified patent counsel.

Core Features & Use Cases

  • Patent Risk Triage: Evaluate supplied patents or preliminary search results against a product, process, or feature.
  • Claim-Chart First Pass: Map every element of the most plausible independent claims to the product, while separating literal infringement, doctrine-of-equivalents, indirect infringement, and divided-infringement considerations.
  • Counsel-Ready Memo: Record search scope, patent details, open questions, work-product protections, willfulness considerations, and recommended next steps for patent counsel review.
  • Use Case: Before launching an on-device speech recognition feature in the United States, provide its technical architecture and any known patents to produce an element-by-element triage memo and identify design-around or licensing questions.

Quick Start

Use the fto-triage skill to assess potential blocking patents for the product, process, or feature, including its technical details, jurisdictions, known patents, and launch timing.

Frequently Asked Questions about fto-triage

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

FAQPage Schema
How do I identify blocking utility patents before launching a new product feature?

To identify blocking utility patents before launch, you need an element-by-element claim mapping triage that compares your product's technical architecture against independent claims to surface literal infringement and doctrine-of-equivalents risks.

What is the best way to prepare a preliminary freedom-to-operate analysis for patent counsel?

The best way to prepare a preliminary freedom-to-operate analysis is to generate a counsel-ready memo documenting search scope, patent status verification, open questions, willfulness considerations, and recommended next steps for qualified patent counsel review.

How does claim chart mapping work for assessing patent infringement risk?

Claim chart mapping for infringement risk works by evaluating each element of the most plausible independent claims against your product details, systematically separating literal infringement, doctrine-of-equivalents, indirect infringement, and divided-infringement considerations.

Can I use patent triage to plan design-around strategies for existing patents?

Yes, you can use patent triage to plan design-around strategies by mapping supplied patent claims against your process or feature specifications to identify specific claim elements that require alternative technical implementations.

Do I need a qualified patent attorney after completing a preliminary patent risk triage?

Yes, you need a qualified patent attorney because preliminary patent risk triage explicitly avoids presenting results as a freedom-to-operate opinion and is designed to route decisions and open questions to qualified patent counsel for final legal review.

What limitations exist when using automated tools for freedom-to-operate reviews?

Limitations of freedom-to-operate reviews include the inability to provide legal opinions, the requirement for accurate product technical details and jurisdiction timing, and the necessity to verify patent status across specified jurisdictions before making launch decisions.