specification-writing

Draft patent specifications from claims and invention disclosures.

Updated Jun 10, 2026
One-click install
npx skills add https://github.com/xqinag/ARIS-new --skill specification-writing-xqinag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specification-writing
Source: https://github.com/xqinag/ARIS-new/tree/main/skills/specification-writing
Command: npx skills add https://github.com/xqinag/ARIS-new --skill specification-writing-xqinag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafting a complete patent specification from claims and invention disclosures is labor-intensive and error-prone. This skill automates and standardizes the process, ensuring technical rigor, full claim support, and jurisdiction-ready documentation.

Core Features & Use Cases

  • Structured drafting workflow: generates the standard patent sections (title, technical_field, background, summary, drawings_description, detailed_description, abstract) from inputs such as CLAIMS.md, INVENTION_DISCLOSURE.md, and PRIOR_ART_REPORT.md.
  • Claim support verification: cross-checks every claim element against the detailed description to ensure enablement and coherence.
  • Multijurisdiction readiness: supports language and formatting rules per jurisdiction and prepares documents suitable for filing.
  • Variants and embodiments: supports multiple embodiments and variations to broaden protection and interpretation scenarios.

Use cases include: drafting a new patent specification from an invention disclosure, updating an existing patent spec where claims have changed, and generating a prior art-informed background section to accompany an IDS.

Quick Start

Generate a complete patent specification from CLAIMS.md and INVENTION_DISCLOSURE.md, verify all claims are fully supported, and export a filing-ready document.

Frequently Asked Questions about specification-writing

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

FAQPage Schema
How do I draft a patent specification from claims and an invention disclosure?

Drafting a patent specification from claims and disclosures is automated by structuring inputs like CLAIMS.md and INVENTION_DISCLOSURE.md into standard sections including background, summary, and detailed description. This process ensures full claim support and jurisdiction-ready filing documentation.

What is the best way to ensure patent claims are fully supported in the detailed description?

Ensuring patent claims are supported involves cross-checking every claim element against the detailed description to verify enablement and coherence. This automated verification step enforces explicit support for each feature, guaranteeing the specification meets technical and legal filing requirements.

Can I generate prior art-informed background sections for a patent application?

Generating a prior art-informed background section is supported by processing a PRIOR_ART_REPORT.md input alongside invention disclosures. This produces a coherent background section that contextualizes the invention against existing prior art to accompany an Information Disclosure Statement (IDS).

Does this patent drafting workflow support multiple jurisdictions and formatting rules?

Patent drafting across multiple jurisdictions is supported by applying language and formatting rules specific to each jurisdiction. This multijurisdiction readiness ensures the generated specification complies with regional filing requirements and produces a ready-for-submission document.

How do I update an existing patent specification when claims have changed?

Updating an existing patent specification when claims change is handled by reprocessing the new CLAIMS.md against the previous invention disclosures. The workflow regenerates the necessary sections and verifies that the updated claims are fully supported by the detailed description.

Can I include multiple embodiments and variations in a patent specification?

Including multiple embodiments and variations in a patent specification is supported to broaden protection and interpretation scenarios. The drafting workflow integrates these variants into the detailed description, ensuring every claimed feature is explicitly enabled across different implementations.