invention-structuring

Structure raw invention ideas into formal patent disclosure documents.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/Lingjie-wang/autoRL --skill invention-structuring-lingjie-wang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: invention-structuring
Source: https://github.com/Lingjie-wang/autoRL/tree/main/Auto-claude-code-research-in-sleep/skills/invention-structuring
Command: npx skills add https://github.com/Lingjie-wang/autoRL --skill invention-structuring-lingjie-wang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough invention idea into a formal, patent-ready disclosure requires legal structuring expertise that most inventors and engineers lack, often resulting in weak claims or missed claimable subject matter. ## Core Features & Use Cases - Problem-Solution-Advantage Framework: Derives the technical problem from prior art deficiencies and formalizes the solution and measurable advantages. - Three-Layer Decomposition: Breaks the invention into core inventive concept, supporting features, and optional features mapped to independent claims, dependent claims, and embodiments. - Claim and Drawing Planning: Identifies claimable subject matter categories (method, system, product, medium), plans supporting figures, and maps claim dependency hierarchies. - Use Case: After completing prior art research and novelty assessment, feed your invention brief into this Skill to produce a structured INVENTION_DISCLOSURE.md with claim hierarchy and drawing plan, validated by a cross-model patent attorney review. ## Quick Start Structure my invention described in patent/INVENTION_BRIEF.md into a formal invention disclosure with claim planning.

Frequently Asked Questions about invention-structuring

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

FAQPage Schema
How do I structure an invention idea into a patent disclosure?

Apply the Problem-Solution-Advantage framework: derive the technical problem from prior art deficiencies, describe the technical solution's mechanism, and state measurable advantages. Then decompose the invention into core inventive concept, supporting features, and optional features mapped to claim types.

What is the difference between core inventive concept and supporting features?

The core inventive concept is the minimal feature set that makes the invention patentable and maps to the independent claim scope. Supporting features make the invention work well in practice and become dependent claim material that narrows scope while adding value.

What inputs does invention structuring require?

It accepts an invention description as an argument and optionally reads patent/INVENTION_BRIEF.md, patent/PRIOR_ART_REPORT.md, and patent/NOVELTY_ASSESSMENT.md. The prior art and novelty documents ground the technical problem statement in actual prior art deficiencies.

What claim categories should a patent disclosure include?

Depending on the invention, claims can cover method/process steps, system/apparatus components, physical products, computer-readable media for software, or product-by-process when structure is hard to define. The disclosure should identify all applicable categories to avoid missing claimable subject matter.

What happens if the cross-model validation tool is unavailable?

If the mcp__codex__codex reviewer is not available, the Skill skips the cross-model validation step and notes the omission in the output. The invention disclosure is still generated with the full structuring, decomposition, and claim planning workflow.