nature-paper-to-patent

Paper to Chinese Patent

Use this file as the router for the patent-drafting workflow. Do not draft the application directly from the paper abstract or contribution list.

1. Load the workflow

Read manifest.yaml, then read every file under always_load.

Detect these axes from the user's files and request:

• source_format: selectable PDF, scanned PDF, pasted text, or mixed project;
• task_mode: full draft, claim set, disclosure analysis, technical disclosure, disclosure iteration, or paper-patent audit;
• invention_type: algorithm/software, apparatus/system, process/material, or mixed.

State the detected values in one short line. Load only the matching fragments declared in the manifest. Load detailed references only when their condition applies.

2. Preserve source grounding

Create stable source IDs before drafting:

• P001... for paper text blocks;
• E001... for equations;
• F001... for source figures;
• C001... for source-code or supplementary evidence.

Every material feature in a formal claim must map to one or more source IDs. Use only explicit, inherent, needs-confirmation, or unsupported as support states. Exclude unsupported features from formal claims.

Never infer inventorship, ownership, unpublished implementation details, publication dates, prior-art conclusions, or legal sufficiency. Use [TO CONFIRM: specific question] outside formal claims when facts are missing.

3. Draft through stage gates

For full-draft, claim-set, disclosure-analysis, and paper-patent-audit, complete the stages in static/core/workflow.md in order. Persist the intermediate artifacts specified there. Do not move to formal claims until the source map, terminology ledger, inventories, evidence ledger, and invention concept pass their gates.

For technical-disclosure, follow the ordered prompt references in static/fragments/task/technical-disclosure.md. For disclosure-iteration, follow static/fragments/task/disclosure-iteration.md and preserve the prior draft instead of restarting the formal application workflow.

For a full application, draft claims first, then align the specification, figures, embodiments, and abstract to the claim terminology and step order.

4. Produce Chinese formal documents

Agent-facing analysis may use the user's preferred language. Produce formal Chinese patent deliverables in Chinese when the task is a formal application package:

• 权利要求书;
• 说明书;
• 说明书摘要;
• 摘要附图;
• figure labels and descriptions.

For technical-disclosure and disclosure-iteration, produce the Chinese technical disclosure (技术交底书) as timestamped Markdown plus matching DOCX, with Mermaid system/process diagrams rendered through scripts/disclosure/.

For algorithmic inventions, retain source-supported core formulas, define every symbol, explain each formula's technical operation, and render formulas as native editable Office Math in DOCX. Do not use plain LaTeX strings as the visible formula.

Generate the main flowchart from the ordered steps of the principal method claim. Its final node must name the concrete domain output, such as a defect detection result, target pose, state estimate, or control instruction. Reuse the same main figure as the abstract figure and a specification figure.

5. Validate before delivery

For formal application packages, populate the structured draft described in references/draft-schema.md, then run:

python scripts/validate_patent_draft.py draft.json
python scripts/build_patent_package.py draft.json --output-dir outputs --prefix patent

Resolve all validation ERROR findings. Review every WARNING against the source. Label the result incomplete draft when a required quality threshold in static/core/output-contract.md is not met.

For technical disclosures, run the internal checks in references/disclosure/disclosure_self_check.md, render Mermaid/Word outputs with scripts/disclosure/mermaid_render.py, and resolve formula, parameter, prior-art URL, and chapter-consistency issues before delivery.

The generated package is a drafting aid for inventor and patent-professional review, not a patentability opinion, infringement opinion, or filing guarantee.

---

nature-paper-to-patent 技能

English

nature-paper-to-patent 用于把科研论文、学位论文、技术报告、源代码、图表或发明人笔记转换为证据约束的中国发明专利草稿，也支持从项目文档与代码中挖掘专利点并生成可交给代理人继续修改的中文技术交底书。

适合用它做什么

• 从论文或技术资料中识别可专利化技术贡献。
• 扫描项目文档、代码、Word、PPT，形成候选专利点并融合为一篇技术交底书。
• 优先使用国知局公布公告站并结合公开链接做现有技术查新。
• 生成含 Mermaid 系统框图/流程图的交底书 .md 与 .docx。
• 在已有交底书上继续合并材料、纠错、调整保护点，并保留时间戳版本与修订记录。
• 建立 source ID 和 evidence ledger，再起草权利要求。
• 将算法、装置、系统、工艺、材料或混合型发明路由到对应规则。
• 生成权利要求书、说明书、摘要、摘要附图和完整审阅稿。
• 检查每个权利要求特征是否能回溯到来源证据。

典型请求

• “把这篇论文转成中国发明专利交底书和权利要求草稿。”
• “扫一下这个项目，挖几个专利点，生成技术交底书。”
• “基于这版交底书补充新材料，另存一版 Word。”
• “只提取可专利点，先不要写完整说明书。”
• “对比论文 claim 和专利 claim，看看哪些技术特征缺证据。”

你需要提供

• 论文 PDF、技术报告、代码、图表、实验记录或发明人补充说明。
• 希望保护的对象：方法、系统、装置、材料、工艺或软件流程。
• 已知现有技术、不能公开的信息和必须保留的术语。

产出

• 技术问题、技术方案、实施链条和有益效果分析。
• 技术交底书 Markdown / Word，含查新结论、系统框图、流程图、公式与参数一致性自检。
• 权利要求草稿及每个特征的证据映射。
• 说明书、摘要、附图说明和黑白流程图。
• 可选 DOCX、SVG、PNG 和审阅报告。

运行和依赖

• 完整功能依赖技能目录中的 manifest.yaml、static/、references/、scripts/ 和 requirements.txt。
• 需要生成 DOCX、公式或流程图时，会使用本机 Python 依赖和脚本。
• 交底书分支的 Office 转换、Mermaid 渲染、国知局查新脚本位于 scripts/disclosure/；可选国知局检索依赖见 scripts/disclosure/requirements-cnipa.txt。

边界

• 这是技术起草辅助，不替代专利代理师或法律意见。
• 不会虚构实施例、实验数据、权利要求特征或现有技术对比。
• 证据不足的特征会被标记为缺口，而不是写进主权利要求。

相关技能

• nature-reader：先把论文转成可追溯阅读材料。
• nature-writing：提炼论文贡献和技术叙事。
• nature-figure：生成专利流程图或结构示意图草稿。