/review-claims

description: Analyze patent claims for 35 USC 112(b) compliance - antecedent basis, definiteness, and claim structure
allowed-tools: Bash, Read, Write

Review Patent Claims

Automated analysis of patent claims for USPTO compliance with detailed issue reporting and fixes.

What This Command Does

Performs comprehensive automated claims analysis:

1. **Antecedent Basis Checking**:

• Finds terms used without prior introduction
• Detects "said/the" used before "a/an"
• Tracks term usage across claims

2. **Definiteness Analysis** (35 USC 112(b)):

• Identifies subjective/indefinite terms
• Detects relative terms without reference
• Finds ambiguous language

3. **Claim Structure Validation**:

• Parses independent vs. dependent claims
• Validates dependencies
• Checks claim numbering

4. **Issue Categorization**:

• **Critical**: Must fix before filing
• **Important**: May cause rejection
• **Minor**: Best practice improvements

Who This Is For

• Patent attorneys reviewing draft claims
• Inventors before filing
• Responding to 112(b) office action rejections
• Quality assurance before USPTO submission

Process

Step 1: Provide Claims

You can provide claims in three ways:

**Option 1: Paste claims directly**

/review-claims

> Paste your claims text, then type 'END' on a new line:

What is claimed is:

1. A system comprising:
    a processor;
    a memory; and
    said processor configured to execute instructions.

END

**Option 2: Point to a file**

/review-claims path/to/claims.txt

**Option 3: Let me read from current conversation**

[You paste claims in chat]

/review-claims --from-context

Step 2: Automated Analysis

I'll run the claims through the automated analyzer:

from mcp_server.claims_analyzer import ClaimsAnalyzer
analyzer = ClaimsAnalyzer()
results = analyzer.analyze_claims(claims_text)

This checks:

• All terms for antecedent basis
• All language for definiteness
• Claim structure and dependencies
• Cross-references and pointers

Step 3: Generate Report

I'll provide a detailed compliance report with:

• Overall compliance score (0-100)
• Issue count by severity
• Specific issues with locations
• MPEP citations
• Suggested fixes

Step 4: Fix Issues (Optional)

For each critical/important issue, I can:

• Show the problematic text
• Explain why it's an issue
• Suggest specific fix
• Apply fix if you approve

Report Structure

CLAIMS COMPLIANCE REPORT
========================

Summary:
--------
- Total Claims: 20 (3 independent, 17 dependent)
- Compliance Score: 72/100
- Total Issues: 15 (3 critical, 8 important, 4 minor)

Recommendation: FIX CRITICAL ISSUES BEFORE FILING

CRITICAL ISSUES (Must Fix):
===========================

[Claim 1, Line 3] Antecedent Basis Error
-----------------------------------------
Issue: Term 'processor' used with 'said' before first introduction

Location:
  "said processor configured to execute instructions"
   ^^^^

Problem:
  The term "processor" is used with "said" but was not previously
  introduced with "a" or "an". This violates 35 USC 112(b).

MPEP Citation: MPEP § 2173.05(e) - Antecedent Basis

Fix Suggestion:
  Change "said processor" to "the processor" since it was
  introduced with "a processor" earlier in the claim.

  BEFORE: "said processor configured to..."
  AFTER:  "the processor configured to..."

---

[Claim 5, Line 2] Indefinite Term
----------------------------------
Issue: Subjective term "substantially" without definition

Location:
  "substantially similar to the reference data"
   ^^^^^^^^^^^^

Problem:
  The term "substantially" is subjective and may render the
  claim indefinite under 35 USC 112(b). What degree of
  similarity is "substantial"?

MPEP Citation: MPEP § 2173.05(b) - Subjective Terms

Fix Suggestions:
  Option 1: Define in specification
    Add to spec: "As used herein, 'substantially similar'
    means having at least 95% similarity..."

  Option 2: Use objective criteria
    Change to: "having at least 95% similarity to..."

  Option 3: Remove subjectivity
    Change to: "matching the reference data"

---

[Continue for all critical issues...]

IMPORTANT ISSUES (Should Fix):
==============================

[Claim 3] Weak Antecedent
-------------------------
Issue: Term introduced with "the" instead of "a"

Location: "the communication interface"

While not necessarily indefinite, USPTO examiners prefer
"a communication interface" for first introduction.

Suggested Fix: Change "the" to "a"

---

[Continue for all important issues...]

MINOR ISSUES (Consider Fixing):
===============================

[Claim 10] Style Issue
---------------------
Issue: Using "and/or" can be ambiguous

Location: "processor and/or controller"

While not indefinite, "and/or" can lead to claim
interpretation issues. Consider being more specific.

Suggested Fix: Choose "processor or controller" or
"processor, controller, or both"

---

[Continue for all minor issues...]

CLAIM STRUCTURE ANALYSIS:
=========================

Independent Claims:
  - Claim 1 (system claim): OK
  - Claim 8 (method claim): OK
  - Claim 15 (apparatus claim): OK

Dependent Claims:
  - Claims 2-7 depend from Claim 1: OK
  - Claims 9-14 depend from Claim 8: OK
  - Claims 16-20 depend from Claim 15: OK

Dependency Chain: VALID (no circular dependencies)

MPEP GUIDANCE:
==============

Relevant MPEP Sections:
- MPEP § 2173.05(e) - Antecedent Basis
- MPEP § 2173.05(b) - Subjective Terms
- MPEP § 2111 - Claim Definiteness
- MPEP § 608.01(n) - Antecedent Basis Requirements

NEXT STEPS:
===========

1. FIX all 3 critical issues (required before filing)
2. REVIEW all 8 important issues (recommended fixes)
3. CONSIDER 4 minor issues (optional improvements)
4. RE-RUN analysis after fixes to verify compliance

Interactive Fixing

After the report, I can interactively help you fix issues:

> Found 3 critical issues. Would you like me to help fix them?