specification

Drafts patent specification sections and abstract, then assembles them into a draft.md deliverable.

2|Updated Aug 9, 2026
One-click install
npx skills add https://github.com/DeepJH/doubao-skill-and-info --skill specification-deepjh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specification
Source: https://github.com/DeepJH/doubao-skill-and-info/tree/main/skills/doubao-patent-drafting/sub-skills/specification
Command: npx skills add https://github.com/DeepJH/doubao-skill-and-info --skill specification-deepjh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing a Chinese patent specification (background, invention content, embodiments, figure descriptions, abstract) that stays consistent with the claims and the invention disclosure is error-prone: facts get overstated, figure references get missed, and sections drift apart. This Skill enforces disciplined drafting rules and assembles everything into a single structured draft.md file. ## Core Features & Use Cases - Section-by-section drafting rules: Covers background art, invention content (problem/solution/effects), detailed embodiments, figure descriptions, and abstract, with utility-model title variants handled automatically. - Fact-grading discipline: Maps A/B/C evidence levels from the intake audit to calibrated wording (e.g., tested data vs. design targets), preserving disclosed numeric values with proper qualifiers. - Five-anchor consistency check: Cross-reads abstract, background, technical problem, independent claim, and main effect to verify problem-feature-effect alignment before finalizing. - Use Case: After claims are finalized in a patent drafting workflow, invoke this stage to write the full specification and abstract, then compile case header, review notes, abstract, claims, and specification into one draft.md ready for the build step. ## Quick Start Ask the assistant to proceed to stage three of the patent drafting workflow to write the specification and abstract and assemble the complete draft.md from the finalized claims.

Frequently Asked Questions about specification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a patent specification that stays consistent with the claims?

Rewrite each claim as a corresponding technical solution paragraph in the invention content section, with independent claims mapping to the base solution and dependent claims to progressive solutions. Then run a five-anchor cross-read of abstract, background, technical problem, independent claim, and main effect to verify alignment.

How should untested technical effects be worded in a patent application?

Use hedged wording such as "capable of" or "design target" for effects without test data, and explicitly mark design expectations as pending verification. Only measured data may be stated as tested results, and such paragraphs should end with an applicability limitation sentence.

What sections does a Chinese invention patent specification contain?

The standard structure is invention title, technical field, background art, invention content, figure descriptions (when drawings exist), and detailed embodiments. Utility model applications use the heading "utility model content" instead of "invention content".

How do I handle missing figure drawings in a patent draft?

Declare planned figure names in the figure description section with a note that formal drawings are pending, then reference each planned figure in the embodiments with "as shown in Figure N". Every declared figure must be cited in the body text, and unreferenceable figures should be removed.

What are the limits of this specification drafting stage?

It does not run independently; it requires the intake audit from stage one and finalized claims from stage two. It also does not perform novelty searches or make patentability conclusions, and it stops at producing draft.md for the downstream build step.