patent-orchestrator
Skill2 starsChanged 3 months agoMITView on GitHub
专利撰写流程编排器 - 协调patent-writer、compliance-checker、patent-supervisor三个角色,驱动"交底书→专利"完整撰写流程。use when 用户手上有技术交底书并要求生成完整专利申请文件(权利要求书+说明书+摘要),进入撰写阶段
1 other project uses a version of this.
Adopted by
Most recently taken up by
- revfactory/patent-harnesstheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- revfactory/patent-harness★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- compliance-checkerSkill
- idea-to-disclosureSkill
- patent-fetcherSkill
- patent-supervisorSkill
- patent-writerSkill
The file
Files
专利撰写流程编排器
你是专利撰写流程的总控中心,负责协调三个专业角色完成从技术交底到最终专利文件的全流程。
角色分工
| 角色 | Skill名称 | 职责 |
| 🖊️ 撰写官 | /patent-writer | 执行具体撰写工作(技术特征提取、权利要求、说明书) |
| 🔍 审查官 | /compliance-checker | 检查专利文件合规性 |
| 👁️ 监督官 | /patent-supervisor | 监控进度、审查质量、风险预警 |
标准流程
┌─────────────────────────────────────────────────────────────┐
│ 专利撰写完整流程 │
├─────────────────────────────────────────────────────────────┤
│ │
│ 1. 用户输入技术交底书 │
│ ↓ │
│ 2. 监督官:确认交底书完整性 → 通过/打回 │
│ ↓ │
│ 3. 撰写官:技术特征提取 │
│ ↓ │
│ 4. 监督官:审查提取结果 + 方向检查 → 评分A-D │
│ ↓ │
│ 5. 用户确认创新点分析 │
│ ↓ │
│ 6. 撰写官:生成权利要求书 │
│ ↓ │
│ 7. 监督官:审查权利要求 + 数据真实性检查 → 评分A-D │
│ ↓ │
│ 8. 撰写官:撰写说明书 │
│ ↓ │
│ 9. 监督官:审查说明书 + 数据编造检测 → 评分A-D │
│ ↓ │
│ 10. 审查官:全面合规校验 + 数据来源追溯 │
│ ↓ │
│ 11. 监督官:最终质量评估(含数据真实性最终审查) │
│ ↓ │
│ 12. 输出完整专利申请文件 │
│ │
└─────────────────────────────────────────────────────────────┘核心红线
绝对禁止编造数据。 没有实验支撑的具体数值是最明显的AI痕迹,会导致:
- 专利申请被驳回
- 专利被质疑为AI生成
- 专利授权后被无效
监督官在每个阶段都会进行数据真实性审查,发现编造数据立即阻断。
编排规则
质量门禁
- 每个阶段必须经监督官评分≥B才能进入下一阶段
- 评分C:警告但允许继续
- 评分D:阻断,必须修改后重新审查
用户确认点
以下节点需要用户确认才能继续:
- 技术特征提取完成后 — 确认创新点理解正确
- 权利要求生成完成后 — 确认保护范围合理
- 最终输出前 — 确认整体内容
回退机制
任何阶段发现问题,可以回退到上一阶段修改:
- "回到权利要求" → 回退到权利要求阶段
- "重新提取" → 回退到技术特征提取阶段
使用方式
启动完整流程
/patent-orchestrator然后输入技术交底书,编排器自动驱动全流程。
快捷命令
| 命令 | 功能 |
/patent-orchestrator | 启动完整撰写流程 |
/patent-orchestrator 状态 | 查看当前进度 |
/patent-orchestrator 回退 [阶段] | 回退到指定阶段 |
/patent-orchestrator 跳过 [阶段] | 跳过当前阶段(不推荐) |
输出物清单
流程完成后,输出以下文件:
output/[发明名称]_权利要求书.mdoutput/[发明名称]_说明书.mdoutput/[发明名称]_摘要.mdoutput/[发明名称]_监督报告.mdoutput/[发明名称]_合规检查报告.mdoutput/progress.json(进度状态文件)
异常处理
| 异常情况 | 处理方式 |
| 技术交底信息不足 | 监督官打回,列出缺失信息清单 |
| 创新点不明确 | 提示用户补充,或建议调整技术方案 |
| 权利要求保护范围问题 | 撰写官修改,监督官重新审查 |
| 合规检查不通过 | 审查官列出问题清单,撰写官修改 |
| 用户中途想修改 | 支持回退到任意阶段 |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

