Patent Doc Writer

Problem

Turning a technical solution into a patent specification is often hard because the document must combine legal formatting, claim structure, implementation details, and a clear mapping between method and system claims. Engineers may have a design doc, discussion notes, or requirements, but lack a draft that follows CNIPA conventions.

How It Works

The skill generates the invention patent specification in chapter order. It first collects elements such as invention name, technical field, problem solved, core solution, system modules, and beneficial effects, then drafts the abstract, background, invention content, drawings description, specific implementation, and claims.

• Claims: It produces method independent claims, method dependent claims, system independent claims, and system dependent claims, with emphasis on characterized-in-that phrasing and correct antecedent references.
• Implementation: It uses step labels like S101 and S102, and expects concrete parameters such as frame rate, resolution, or thresholds instead of generic preset values.
• Deliverable: It creates a .docx file using python-docx, followed by a checklist covering abstract length, claim counts, beneficial effects, drawing descriptions, and standard paragraphs.

Boundaries

It is best suited for method and system invention patent drafts in software, electronics, communications, and IoT. The input still needs enough technical detail; vague descriptions like automatic recognition require follow-up on steps, modules, and effects. If the solution processes data, it should also state local processing, privacy safeguards, and security boundaries. It does not replace patent attorney search, office action responses, or legal judgment.