Back to Details

specification-writing

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Specification Writing: Section-by-Section Patent Description

说明书撰写：分节式专利说明文档

Write the patent specification based on: $ARGUMENTS
Adapted from 
/paper-write
for patent specifications. The specification supports the claims -- it is not a paper.
基于**$ARGUMENTS**撰写patent specification。
本功能由
/paper-write
适配而来，专用于patent specification撰写。说明书是权利要求书的支撑文件，而非学术论文。

Constants

常量定义

  • REVIEWER_MODEL = gpt-5.4
    — External reviewer for specification quality
  • JURISDICTION = "auto"
    — Inherit from pipeline or detect from args; 
    CN
    , 
    US
    , 
    EP
    , 
    ALL
  • OUTPUT_FORMAT = "markdown"
    — Markdown drafts; converted to filing format by 
    /jurisdiction-format
  • OUTPUT_DIR = "patent/"
    — Base output directory
  • LANGUAGE = "auto"
    — Auto from jurisdiction: CN->Chinese, US/EP->English
  • REVIEWER_MODEL = gpt-5.4
    — 用于审核说明书质量的外部评审模型
  • JURISDICTION = "auto"
    — 继承自工作流或从参数中自动检测；可选值：
    CN
    、
    US
    、
    EP
    、
    ALL
  • OUTPUT_FORMAT = "markdown"
    — 生成Markdown格式草稿；可通过
    /jurisdiction-format
    转换为提交格式
  • OUTPUT_DIR = "patent/"
    — 基础输出目录
  • LANGUAGE = "auto"
    — 根据司法管辖区自动适配：CN->中文，US/EP->英文

Inputs

输入文件

  1. patent/CLAIMS.md
    — the drafted claims (primary source)
  2. patent/INVENTION_DISCLOSURE.md
    — invention decomposition
  3. patent/PRIOR_ART_REPORT.md
    — for background section
  4. User-provided figures (if any)
  1. patent/CLAIMS.md
    — 已起草的权利要求书（主要来源）
  2. patent/INVENTION_DISCLOSURE.md
    — 发明分解文档
  3. patent/PRIOR_ART_REPORT.md
    — 用于背景技术章节
  4. 用户提供的附图（如有）

Shared References

共享参考资料

Load 
../shared-references/patent-writing-principles.md
for specification writing rules, language guidelines, and reference numeral conventions. Load 
../shared-references/patent-format-cn.md
or 
patent-format-us.md
or 
patent-format-ep.md
based on jurisdiction.
加载
../shared-references/patent-writing-principles.md
以获取说明书撰写规则、语言规范和参考编号约定。 根据司法管辖区加载
../shared-references/patent-format-cn.md
、
patent-format-us.md
或
patent-format-ep.md
。

Workflow

工作流程

Step 1: Initialize Specification Structure

步骤1：初始化说明书结构

Create the output directory and section files:
patent/specification/
├── title.md
├── technical_field.md
├── background.md
├── summary.md
├── drawings_description.md
├── detailed_description.md
└── abstract.md
创建输出目录及各章节文件：
patent/specification/
├── title.md
├── technical_field.md
├── background.md
├── summary.md
├── drawings_description.md
├── detailed_description.md
└── abstract.md

Step 2: Write Title (发明名称)

步骤2：撰写发明名称（Title）

  • Must match the broadest claim scope
  • No trademarks, no "improved" or "new" or "novel"
  • CN format: "一种[领域]的[技术主题]" or "[领域]的[技术主题]装置"
  • US/EP format: "[Technical topic] for [purpose]" or "[Technical topic] and method thereof"
  • Keep concise (CN: typically under 25 characters; US: under 500 characters)
  • 必须与最宽泛的权利要求范围匹配
  • 不得包含商标，不得使用“改进的”“新型的”“新颖的”等词汇
  • 中国格式：“一种[领域]的[技术主题]”或“[领域]的[技术主题]装置”
  • 美国/欧洲格式：“[Technical topic] for [purpose]”或“[Technical topic] and method thereof”
  • 保持简洁（中国：通常不超过25个汉字；美国：不超过500个字符）

Step 3: Write Technical Field (技术领域)

步骤3：撰写技术领域（Technical Field）

1-2 paragraphs identifying the technical domain:
  • "The present invention relates to [broad field], and more particularly to [specific area]."
  • CN: "本发明涉及[技术领域]，具体涉及[具体领域]。"
1-2段文字明确技术领域：
  • 英文表述："The present invention relates to [broad field], and more particularly to [specific area]."
  • 中文表述："本发明涉及[技术领域]，具体涉及[具体领域]。"

Step 4: Write Background (背景技术)

步骤4：撰写背景技术（Background）

This is NOT a literature review. It directly sets up the problem.
Structure:
  1. Describe the closest prior art approaches (2-3 paragraphs)
  2. Identify specific technical deficiencies of each approach
  3. The deficiencies must be technical, not commercial or social
  4. DO NOT admit the prior art is "superior" or "better"
  5. DO NOT cite specific patent numbers unless they are known prior art (citations go in IDS for US, or Background section for CN)
CN format: "背景技术" section describing existing technology and its shortcomings.
本章节并非文献综述，需直接引出待解决的问题。
结构：
  1. 描述最接近的现有技术方案（2-3段）
  2. 指出每种方案存在的具体技术缺陷
  3. 缺陷必须是技术性的，而非商业或社会性的
  4. 不得承认现有技术“更优”或“更好”
  5. 除非是已知的现有技术，否则不得引用具体专利号（美国需将引用内容放入IDS，中国可放入背景技术章节）
中国格式：“背景技术”章节需描述现有技术及其不足。

Step 5: Write Summary (发明内容)

步骤5：撰写发明内容（Summary）

Three parts, directly mirroring INVENTION_DISCLOSURE.md:
Technical Problem (要解决的技术问题):
  • State the problem derived from background deficiencies
  • CN: "本发明要解决的技术问题是..."
Technical Solution (技术方案):
  • Describe how the invention solves the problem
  • Must provide support for ALL claim elements
  • Start from the broadest claim and describe the core inventive concept
  • CN: "为解决上述技术问题，本发明采用的技术方案是：..."
  • NO formulas, NO mathematical derivations, NO circuit models — these belong in 具体实施方式, not 发明内容
Advantages (有益效果):
  • Benefits derived from the structural/technical features (qualitative reasoning)
  • CN: "本发明的有益效果是：..."
  • NO specific numerical results (e.g., "detection limit 70μm", "response time 105ms") — these are experimental findings, not invention properties
  • Frame advantages structurally: "由于采用了...结构，因此具有...效果"
分为三部分，与
INVENTION_DISCLOSURE.md
直接对应：
要解决的技术问题（Technical Problem）：
  • 基于背景技术中的缺陷阐述待解决的问题
  • 中文表述："本发明要解决的技术问题是..."
技术方案（Technical Solution）：
  • 描述发明如何解决上述问题
  • 必须为所有权利要求要素提供支撑
  • 从最宽泛的权利要求入手，描述核心发明构思
  • 中文表述："为解决上述技术问题，本发明采用的技术方案是：..."
  • 不得包含公式、数学推导、电路模型 — 这些内容属于「具体实施方式」，而非「发明内容」
有益效果（Advantages）：
  • 由结构/技术特征带来的优势（定性推理）
  • 中文表述："本发明的有益效果是：..."
  • 不得包含具体数值结果（如“检测限70μm”“响应时间105ms”）— 这些属于实验结果，而非发明固有属性
  • 需从结构层面阐述优势："由于采用了...结构，因此具有...效果"

Step 6: Write Brief Description of Drawings (附图说明)

步骤6：撰写附图说明（Brief Description of Drawings）

Invoke 
/figure-description
as a sub-skill if user has provided figures:
/figure-description "patent/figures/"
If no user figures, describe what figures should exist based on the claims.
Format:
  • CN: "图1是...的示意图；图2是...的流程图；"
  • US: "FIG. 1 is a block diagram showing...; FIG. 2 is a flowchart illustrating..."
若用户提供了附图，调用子技能
/figure-description
：
/figure-description "patent/figures/"
若未提供用户附图，则根据权利要求描述应包含的附图内容。
格式：
  • 中文："图1是...的示意图；图2是...的流程图；"
  • 英文："FIG. 1 is a block diagram showing...; FIG. 2 is a flowchart illustrating..."

Step 7: Write Detailed Description (具体实施方式)

步骤7：撰写具体实施方式（Detailed Description）

Invoke 
/embodiment-description
as a sub-skill:
/embodiment-description "patent/CLAIMS.md"
This section must:
  • Describe at least one complete embodiment with reference numerals
  • Enable a POSITA to make and use the invention
  • Support every claim element with explicit description
  • Include variations and alternatives for broader claim interpretation
调用子技能
/embodiment-description
：
/embodiment-description "patent/CLAIMS.md"
本章节必须：
  • 结合参考编号描述至少一个完整的实施例
  • 使POSITA（Person of Ordinary Skill in the Art，本领域普通技术人员）能够制造并使用本发明
  • 为每个权利要求要素提供明确的描述支撑
  • 包含用于扩大权利要求解释范围的变体和替代方案

Step 8: Write Abstract (摘要)

步骤8：撰写摘要（Abstract）

Jurisdiction-specific word limits:
JurisdictionWord LimitNotes
CN300 words (Chinese characters)Include most representative claim reference
US150 words (2500 characters)Enable efficient searching, no legal phrases
EP~150 wordsNo statements on merits or value
The abstract summarizes:
  1. The technical field
  2. The problem being solved
  3. The technical solution (core features)
  4. Key advantages
不同司法管辖区的字数限制：
司法管辖区字数限制说明
CN300汉字需包含最具代表性的权利要求参考内容
US150单词（2500字符）便于高效检索，不得包含法律术语
EP~150单词不得包含关于发明价值或优点的表述
摘要需涵盖：
  1. 技术领域
  2. 待解决的问题
  3. 技术方案（核心特征）
  4. 关键优势

Step 9: Claim Support Verification

步骤9：权利要求支撑验证

Verify every claim element finds support in the specification:
ClaimElementSpecification SectionParagraph(s)Reference Numeral
1step adetailed_description¶3202
1step bdetailed_description¶4204
Xcomponent Adetailed_description¶2102
If any element lacks support, add the necessary description before proceeding.
验证每个权利要求要素在说明书中均有支撑：
权利要求要素说明书章节段落参考编号
1step adetailed_description¶3202
1step bdetailed_description¶4204
Xcomponent Adetailed_description¶2102
若任何要素缺乏支撑，需先补充必要描述再继续。

Step 10: Cross-Model Review

步骤10：跨模型评审

Call 
REVIEWER_MODEL
via 
mcp__codex__codex
with xhigh reasoning:
mcp__codex__codex:
  config: {"model_reasoning_effort": "xhigh"}
  prompt: |
    You are a patent examiner reviewing a specification for completeness.
    CLAIMS: [all claims]
    SPECIFICATION: [all specification sections]

    Check for:
    1. Written description support: Does every claim element have explicit or inherent support?
    2. Enablement: Can a POSITA practice the invention from this specification?
    3. Consistency: Do reference numerals match across figures and specification?
    4. Language quality: Any subjective terms, relative terms without definition, or result-to-be-achieved language?
    5. Missing embodiments: Are there claim features that need additional embodiments?
    6. Background deficiencies: Are they technical and specific enough?
通过
mcp__codex__codex
调用
REVIEWER_MODEL
，并启用xhigh推理级别：
mcp__codex__codex:
  config: {"model_reasoning_effort": "xhigh"}
  prompt: |
    You are a patent examiner reviewing a specification for completeness.
    CLAIMS: [all claims]
    SPECIFICATION: [all specification sections]

    Check for:
    1. Written description support: Does every claim element have explicit or inherent support?
    2. Enablement: Can a POSITA practice the invention from this specification?
    3. Consistency: Do reference numerals match across figures and specification?
    4. Language quality: Any subjective terms, relative terms without definition, or result-to-be-achieved language?
    5. Missing embodiments: Are there claim features that need additional embodiments?
    6. Background deficiencies: Are they technical and specific enough?

Step 11: Output

步骤11：输出结果

All specification sections are in 
patent/specification/
.
Summary file: 
patent/specification/SPECIFICATION_INDEX.md
with:
markdown
undefined
所有说明书章节均存储于
patent/specification/
目录下。
摘要文件：
patent/specification/SPECIFICATION_INDEX.md
，内容如下：
markdown
undefined

Patent Specification

Patent Specification

Sections

Sections

SectionFileWord CountStatus
Titletitle.mdComplete
Technical Fieldtechnical_field.mdComplete
Backgroundbackground.mdComplete
Summarysummary.mdComplete
Drawings Descriptiondrawings_description.mdComplete
Detailed Descriptiondetailed_description.mdComplete
Abstractabstract.mdComplete
SectionFileWord CountStatus
Titletitle.mdComplete
Technical Fieldtechnical_field.mdComplete
Backgroundbackground.mdComplete
Summarysummary.mdComplete
Drawings Descriptiondrawings_description.mdComplete
Detailed Descriptiondetailed_description.mdComplete
Abstractabstract.mdComplete

Claim Support Status

Claim Support Status

ClaimElements SupportedElements Missing
1AllNone
XAllNone
undefined
ClaimElements SupportedElements Missing
1AllNone
XAllNone
undefined

Key Rules

核心规则

  • The specification supports the claims, not the other way around. Every claim element must have support.
  • Use consistent terminology -- same word for the same concept throughout.
  • DO NOT include experimental results, accuracy metrics, or empirical evaluations.
  • DO NOT use subjective language ("excellent", "surprising", "superior").
  • Reference numerals must be consistent: same component, same numeral, everywhere.
  • Background section describes specific deficiencies, not general "need for improvement."
  • Multiple embodiments strengthen the specification but are not always required.
  • Large file handling: if a Write operation fails, retry with Bash 
    cat <<'EOF'
    heredoc.
  • If 
    mcp__codex__codex
    is not available, skip cross-model review and note it in the output.
  • 说明书是权利要求书的支撑文件，反之则不成立。每个权利要求要素必须有对应的支撑内容。
  • 使用一致的术语 — 同一概念全程使用相同词汇。
  • 不得包含实验结果、精度指标或实证评估内容。
  • 不得使用主观语言（如“优秀的”“惊人的”“更优的”）。
  • 参考编号必须保持一致：同一组件在所有地方使用相同编号。
  • 背景技术章节需描述具体缺陷，而非笼统的“改进需求”。
  • 多个实施例会增强说明书的有效性，但并非始终必需。
  • 大文件处理：若写入操作失败，使用Bash的
    cat <<'EOF'
    heredoc重试。
  • 若
    mcp__codex__codex
    不可用，跳过跨模型评审并在输出中注明。