AgentAlley

Skills · Business & ops

Structure Your Invention For A Patent Filing

Unverified●37/40

Describe your invention in plain words and get back a formal write-up that lays out the problem it solves, how it works, and which parts are worth protecting.

Originally by wanshuiyin · MIT

Claude Code●WorksValid SKILL.md that declares allowed-tools
Cursor·UnknownWe have not crawled the repo tree, so we will not guess
Codex·UnknownWe have not crawled the repo tree, so we will not guess
Gemini CLI·UnknownThe spec defines no detection rule for Gemini
Copilot·UnknownWe have not crawled the repo tree, so we will not guess
npx agentalley add invention-structuring

This command does not work yet — the CLI is still being built. Until then, use Raw in the reader below to take the file.

Who is stuck, and on what

I've come up with something new but I have no idea how to write it up so a patent lawyer takes me seriously. I don't want to pay hundreds an hour just to explain the basics from scratch.

What it gives you

A structured invention disclosure covering the problem it solves, your solution, its advantages, and which parts are the truly protectable core versus nice-to-have extras.

When NOT to use it

It will not file your patent or give legal advice — a qualified patent attorney still needs to review and file everything.

The whole source

No sign-in, no blur, nothing truncated
invention-structuring/SKILL.md189 lines6.6 KBRawView on GitHub
Frontmatter — 4 properties
nameinvention-structuring
descriptionStructure a raw invention idea into a formal invention disclosure. Use when user says \"构建发明\", \"structure invention\", \"发明构建\", \"invention disclosure\", or wants to formalize a rough idea into a patent-ready structure.
argument-hint[invention-description-or-brief-path]
allowed-toolsBash(*), Read, Write, Edit, Grep, Glob, mcp__codex__codex
1---
2name: invention-structuring
3description: "Structure a raw invention idea into a formal invention disclosure. Use when user says \"构建发明\", \"structure invention\", \"发明构建\", \"invention disclosure\", or wants to formalize a rough idea into a patent-ready structure."
4argument-hint: "[invention-description-or-brief-path]"
5allowed-tools: Bash(*), Read, Write, Edit, Grep, Glob, mcp__codex__codex
6---
7 
8# Invention Structuring
9 
10Structure the invention into a formal disclosure based on: **$ARGUMENTS**
11 
12Adapted from the refinement pattern in `/research-refine` for patent invention decomposition.
13 
14## Constants
15 
16- `REVIEWER_MODEL = gpt-6-astra` — External reviewer for invention decomposition validation
17- `MAX_REFINEMENT_ROUNDS = 3` — Maximum structuring iterations
18 
19## Inputs
20 
211. Invention description from `$ARGUMENTS`
222. `patent/INVENTION_BRIEF.md` if exists
233. `patent/PRIOR_ART_REPORT.md` — prior art landscape
244. `patent/NOVELTY_ASSESSMENT.md` — novelty analysis
25 
26## Shared References
27 
28Load `../shared-references/patent-writing-principles.md` for the Problem-Solution-Advantage framework and claimable subject matter guidelines.
29 
30## Workflow
31 
32### Step 1: Problem-Solution-Advantage Framework
33 
34Structure the invention using the universal patent framework:
35 
36**Technical Problem (要解决的技术问题)**:
37- Derived from prior art deficiencies identified in NOVELTY_ASSESSMENT.md
38- Must be a specific, technical problem (not a commercial or social problem)
39- Statement format: "The technical problem to be solved is how to [specific technical objective] given [specific technical constraint]."
40 
41**Technical Solution (技术方案)**:
42- The invention's specific technical contribution
43- Focus on the mechanism, not the result
44- Must be described at a level that matches the intended claim scope
45- Identify which features are known vs. inventive
46 
47**Advantages (有益效果)**:
48- Measurable or quantifiable improvements over prior art
49- Must result from the inventive features, not just good engineering
50- Include specific technical effects if known (e.g., "reduces processing time by 40%")
51 
52### Step 2: Invention Decomposition
53 
54Break the invention into three layers:
55 
56**Core Inventive Concept (核心发明构思)**:
57- The minimal set of features that make the invention patentable
58- This maps to the independent claim scope
59- Test: if you remove this feature, the invention is no longer novel
60 
61**Supporting Features (支撑性特征)**:
62- Features that make the invention work well in practice
63- These become dependent claim material
64- They narrow the scope but add practical value
65 
66**Optional Features (可选特征)**:
67- Implementation details, preferred parameters, alternatives
68- These become embodiment material
69- They support broader claim interpretation
70 
71### Step 3: Claimable Subject Matter Identification
72 
73For the core inventive concept, determine what categories of claims to draft:
74 
75| Category | Applicability | Content |
76|----------|-------------|---------|
77| Method/process | If invention involves steps | Process flow, algorithm, workflow |
78| System/apparatus | If invention involves components | Hardware structure, modules, connections |
79| Product | If invention is a physical device | Shape, structure, composition |
80| Computer-readable medium | If software invention (US) | Stored instructions, non-transitory medium |
81| Product-by-process | If structure is hard to define | Product defined by how it is made |
82 
83### Step 4: Drawing Plan
84 
85Plan what figures are needed to support the claims and specification:
86 
87| Figure | Type | Shows | Supports Claim Elements |
88|--------|------|-------|------------------------|
89| FIG. 1 | Block diagram | System architecture | System claim components |
90| FIG. 2 | Flowchart | Method steps | Method claim steps |
91| FIG. 3 | Sequence diagram | Interaction between components | Specific implementation details |
92 
93If user has provided figures, reference them here. If figures are missing, note what is needed.
94 
95### Step 5: Dependency Mapping
96 
97Map feature dependencies to plan the claim hierarchy:
98 
99```
100Independent Claim 1 (method, broadest scope)
101├── Core inventive feature A
102├── Core inventive feature B
103└── Known feature C (for context)
104 
105Dependent Claim 2 → narrows feature A with specific implementation
106Dependent Claim 3 → narrows feature B with specific parameters
107Dependent Claim 4 → depends on 2, adds optional feature D
108Dependent Claim 5 → alternative implementation of feature A
109```
110 
111### Step 6: Cross-Model Validation
112 
113Call `REVIEWER_MODEL` via `mcp__codex__codex` with xhigh reasoning:
114 
115```
116mcp__codex__codex:
117 model: gpt-6-astra
118 config: {"model_reasoning_effort": "xhigh"}
119 prompt: |
120 You are a patent attorney reviewing an invention disclosure.
121 Evaluate the structuring choices:
122 
123 INVENTION: [Problem-Solution-Advantage summary]
124 DECOMPOSITION: [Core/Supporting/Optional features]
125 CLAIM PLAN: [intended claim categories and hierarchy]
126 
127 Please assess:
128 1. Is the Problem-Solution-Advantage framework correctly applied?
129 2. Is the core inventive concept correctly identified? Are there features that should be core but are listed as supporting (or vice versa)?
130 3. Are the planned claim categories sufficient to protect the invention?
131 4. Is the drawing plan adequate for enablement?
132 5. Are there any claimable aspects being missed?
133```
134 
135### Step 7: Output
136 
137Write `patent/INVENTION_DISCLOSURE.md`:
138 
139```markdown
140## Invention Disclosure
141 
142### Title
143[invention title]
144 
145### Technical Problem
146[formal problem statement]
147 
148### Technical Solution
149[formal solution description]
150 
151### Advantages
152[measurable advantages]
153 
154### Feature Decomposition
155 
156#### Core Inventive Concept
157[features that define independent claim scope]
158 
159#### Supporting Features
160[features for dependent claims]
161 
162#### Optional Features
163[features for embodiments]
164 
165### Claimable Subject Matter
166[method, system, product, medium claims planned]
167 
168### Drawing Plan
169[figures needed, what each shows]
170 
171### Dependency Map
172[claim hierarchy plan]
173 
174### Inventor Information
175[names, contributions]
176 
177### Target Jurisdiction
178[CN/US/EP/ALL]
179```
180 
181## Key Rules
182 
183- The Problem must come from prior art deficiencies, not from commercial needs.
184- The Solution must describe the technical mechanism, not just the result.
185- The core inventive concept must be the minimum set of features for patentability.
186- Supporting features should be independently valuable -- each should provide a meaningful technical benefit even if other supporting features are removed.
187- Never invent embodiments that do not correspond to the actual invention or user-provided materials.
188- If `mcp__codex__codex` is not available, skip cross-model validation and note it in the output.
189 

Reviews

Installed this one?Write the first review and take the Trailblazer badge.

Reviews only open after a real install, so this is empty — and we leave it empty rather than invent one.

Alternatives

Also in Business & ops
Claims Drafting: The Core Patent SkillDescribe your invention in plain words and get back a numbered set of formal patent claims — the legal wording that defines exactly what you own.Business & ops · Business · MIT●····●36/40Patent Novelty and Non-Obviousness CheckDescribe your invention in everyday words and get back a clear read on whether it's new and original enough to patent, plus where it might hit trouble.Business & ops · Business · MIT●····●35/40Patent Pipeline: From Invention to FilingDescribe your invention in plain words and get back a complete first-draft patent application — claims, full description, and abstract — ready to hand to a patent attorney.Business & ops · Business · MIT●····●35/40Codebase ScannerScans the codebase to generate project-doc.md and AGENTS.md. Use when bootstrapping a new agent-driven repo, refreshing project documentation after architectural changes, or running a delta scan to detect drift. Runs a full scan on first use and a smart delta scan on subsequent runs. Uses understand-anything + context-mode when available, falls back to native tools otherwise. Only updates AGENTS.md on detected architectural changes with human confirmation.Business & ops · MIT◐◐◐◐◐●33/40