专利审查
- 作者仓库星标 11,320
- 作者仓库 Auto-claude-code-research-in-sleep
- 领域
- 工程开发
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @wanshuiyin · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
第 1 步:收集专利背景
在致电外部评审员之前,编制一份全面的简报: 阅读所有权利要求(独立 + 从属) 阅读说明书部分(至少摘要和详细描述) 阅读现有技术报告以了解背景 识别:核心发明概念、权利要求范围、已知现有技术、目标管辖权
第 2 步:第 1 轮 — 审查员全面审查
通过 `mcp__codex__codex` 发送至 `REVIEWER_MODEL`,并进行 xhigh 推理:
第 3 步:实施修复(第 1 轮)
根据审查员的审查意见通知书: 关键问题(102 拒绝、112 不确定性、缺少启用): 必须在继续之前解决 修改权利要求或添加规范支持 主要问题(103 显而易见性、弱权利要求范围、缺少支持):
第 4 步:第 2 轮 — 后续审查
将 `mcp__codex__codex` 与第一轮中的 threadId 结合使用:
第 5 步:生成改进报告
写`patent/PATENT_REVIEW.md`:
# Patent Examiner Review via Codex MCP (xhigh reasoning)
Get a multi-round patent examiner review of the patent application based on: **$ARGUMENTS**
Adapted from `/research-review`. The reviewer persona is a patent examiner, not a paper reviewer.
## Constants
- `REVIEWER_MODEL = gpt-5.5` — Model used via Codex MCP
- `REVIEW_ROUNDS = 2` — Number of review rounds
- `EXAMINER_PERSONA = "patent-examiner"` — GPT-5.5 persona
## Prerequisites
- Codex MCP Server configured:
```bash
claude mcp add codex -s user -- codex mcp-server
```
## Inputs
1. `patent/CLAIMS.md` — all drafted claims
2. `patent/specification/` — all specification sections
3. `patent/figures/numeral_index.md` — reference numeral mapping
4. `patent/PRIOR_ART_REPORT.md` — known prior art
5. `patent/INVENTION_DISCLOSURE.md` — invention structure
## Workflow
### Step 1: Gather Patent Context
Before calling the external reviewer, compile a comprehensive briefing:
1. Read all claims (independent + dependent)
2. Read specification sections (at least summary and detailed description)
3. Read prior art report for context
4. Identify: core inventive concept, claim scope, known prior art, target jurisdiction
### Step 2: Round 1 — Full Examiner Review
Send to `REVIEWER_MODEL` via `mcp__codex__codex` with xhigh reasoning:
```
mcp__codex__codex:
config: {"model_reasoning_effort": "xhigh"}
prompt: |
You are a senior patent examiner at the [USPTO/CNIPA/EPO].
Examine this patent application and issue a detailed office action.
CLAIMS:
[all claims]
SPECIFICATION SUMMARY:
[key sections: title, technical field, background, summary, abstract]
PRIOR ART KNOWN:
[prior art references]
PATENTABILITY STANDARDS TO APPLY:
[US: 35 USC 101/102/103/112 | CN: Articles 22, 26 | EP: Articles 54, 56, 83, 84]
Please issue an office action covering:
1. CLAIM CLARITY (112(b)/Art 84):
- Are all terms definite?
- Any indefinite functional language?
- Antecedent basis issues?
2. WRITTEN DESCRIPTION (112(a)/Art 83 first para):
- Does the spec support ALL claim scope?
- Any claim elements without spec support?
3. ENABLEMENT (112(a)/Art 83):
- Can a POSITA practice the invention?
- Any missing algorithm/structure for functional claims?
4. NOVELTY (102/Art 54):
- Would any known reference anticipate any claim?
- Identify the closest single reference.
5. NON-OBVIOUSNESS (103/Art 56):
- Would any combination render claims obvious?
- What is the motivation to combine?
6. CLAIM SCOPE:
- Are independent claims broad enough to be commercially valuable?
- Do dependent claims provide meaningful fallback positions?
- Any claims that are too broad (likely rejected) or too narrow (not valuable)?
7. SPECIFICATION QUALITY:
- Language issues (subjective terms, relative terms, result-to-be-achieved)
- Reference numeral consistency
- Missing embodiments
Format your response as a formal office action with:
- GROUNDS OF REJECTION for each issue (cite statute)
- SUGGESTED AMENDMENTS for each issue
- OVERALL PATENTABILITY SCORE: 1-10
Be rigorous and specific. This is a real examination.
```
### Step 3: Implement Fixes (Round 1)
Based on the examiner's office action:
1. **CRITICAL issues** (102 rejection, 112 indefiniteness, missing enablement):
- Must be fixed before proceeding
- Amend claims or add specification support
2. **MAJOR issues** (103 obviousness, weak claim scope, missing support):
- Should be fixed or argued
- Consider claim amendments or specification additions
3. **MINOR issues** (language quality, numeral consistency, formatting):
- Fix if time permits
- Document in output for later cleanup
For each fix:
- Show the specific change (old claim -> new claim)
- Explain how the fix addresses the examiner's concern
### Step 4: Round 2 — Follow-Up Review
Use `mcp__codex__codex` with the threadId from Round 1:
```
mcp__codex__codex:
threadId: [from Round 1]
prompt: |
Here is the revised patent application after addressing your office action.
CHANGES MADE:
[list of all changes with rationale]
REVISED CLAIMS:
[updated claims]
REVISED SPECIFICATION EXCERPTS:
[changed sections]
Please re-examine:
1. Are the previous rejections overcome?
2. Are there new issues introduced by the amendments?
3. What is the updated patentability score?
4. Any remaining grounds for rejection?
```
### Step 5: Generate Improvement Report
Write `patent/PATENT_REVIEW.md`:
```markdown
## Patent Review Report
### Application Summary
[Title, claims count, jurisdiction]
### Review Round 1
#### Office Action Summary
[Key findings from examiner]
#### Issues Found
| # | Type | Severity | Claim/Section | Issue | Citation | Fix Applied |
|---|------|----------|--------------|-------|----------|-------------|
| 1 | Clarity | CRITICAL | Claim 3 | Indefinite term "rapid" | 112(b) | Defined in spec |
| 2 | Novelty | MAJOR | Claim 1 | Ref X anticipates element C | 102 | Amended claim |
#### Score After Round 1: [X]/10
### Review Round 2
#### Follow-Up Assessment
[Are previous rejections overcome?]
#### Remaining Issues
[Any issues still outstanding]
#### Score After Round 2: [X]/10
### Recommendations
[Final recommendations before proceeding to jurisdiction formatting]
- [ ] All CRITICAL issues resolved
- [ ] All MAJOR issues resolved or argued
- [ ] Specification supports all claim amendments
- [ ] Ready for jurisdiction formatting
```
## Key Rules
- The reviewer persona must be a patent examiner, not a paper reviewer or academic.
- Always use `model_reasoning_effort: "xhigh"` for maximum analysis depth.
- Address CRITICAL and MAJOR issues before proceeding to the next phase.
- Document all changes in the review report for traceability.
- If the patentability score is below 5/10 after Round 2, recommend significant rework before filing.
- The review is advisory -- actual prosecution may proceed differently.
章节与文件索引
按说明文件中的顺序排列。
常数
先决条件
输入
第 1 步:收集专利背景
第 2 步:第 1 轮 — 审查员全面审查
文件/命令 -> /research-review · REVIEWER_MODEL = gpt-5.5 · REVIEW_ROUNDS = 2 · EXAMINER_PERSONA = "patent-examiner" · patent/CLAIMS.md · patent/specification/ · patent/figures/numeral_index.md · patent/PRIOR_ART_REPORT.md
内容校验值 -> b3b0d383711b
当前原文的自动摘译,尚未人工审校。
常数
REVIEWER_MODEL = gpt-5.5— 通过 Codex MCP 使用的模型REVIEW_ROUNDS = 2— 审核轮数EXAMINER_PERSONA = "patent-examiner"— GPT-5.5 角色先决条件
Codex MCP 服务器配置:
输入
patent/CLAIMS.md— 所有起草的权利要求patent/specification/— 所有规格部分patent/figures/numeral_index.md— 附图标记映射patent/PRIOR_ART_REPORT.md— 已知的现有技术patent/INVENTION_DISCLOSURE.md— 发明结构第 2 步:第 1 轮 — 审查员全面审查
通过
mcp__codex__codex发送到REVIEWER_MODEL,并进行 xhigh 推理: