Przejdź do treści
Biblioteka skilli
Prawo i compliance · Pisanie

specification-writing

/specification-writing

Pisze pełny opis patentowy na podstawie zastrzeżeń i ujawnienia wynalazku.

Repozytorium
Athena ↗
Licencja
MIT
Ostatnia zmiana repozytorium
13.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
1
Przestarzałość

Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Pisze pełny opis patentowy na podstawie zastrzeżeń i ujawnienia wynalazku.

Wyzwalacze z opisu

Writing notes\write specification\Write instructions.\patent description\

Argumenty

/specification-writing [claims-path]
Oryginalny opis (EN)

Write the full patent specification from claims and invention disclosure. Use when user says \"Writing notes\", \"write specification\", \"Write instructions.\", \"patent description\", or wants to draft the complete patent specification.

Jak działa

  1. Constants
  2. Inputs
  3. Shared References
  4. Workflow
  5. Key Rules
  6. Mirror description (additional to this open warehouse)
Sekcje z nagłówków SKILL.md, w oryginale · 223 linii, 1 297 słów
Podgląd SKILL.md
---
name: specification-writing
description: "Write the full patent specification from claims and invention disclosure. Use when user says \"Writing notes\", \"write specification\", \"Write instructions.\", \"patent description\", or wants to draft the complete patent specification."
argument-hint: "[claims-path]"
allowed-tools: Bash(*), Read, Write, Edit, Grep, Glob, Skill, WebSearch, WebFetch, mcp__codex__codex, mcp__codex__codex-reply, mcp__antigravity__antigravity, mcp__antigravity__antigravity-reply, mcp__grok__grok, mcp__grok__grok-reply, mcp__claude-review__review, mcp__claude-review__review_reply, mcp__claude-review__review_start, mcp__claude-review__review_reply_start, mcp__claude-review__review_status
---

# Specification Writing: Section-by-Section Patent Description

> **Before each reviewer slot**, follow [Selectable Reviewers](../shared-references/reviewer-backends.md):
> resolve invocation → `.aris/reviewer.json` → Claude Code default (Codex MCP)
> with `reviewer_route.py` through the canonical helper resolver, preserving this
> slot's tier, fresh contexts, source/image inputs and deterministic gates.
> Codex examples/pins below apply only to `backend=codex`; other routes use their
> own first-call/reply contract. Save the route and actual returned identity;
> unavailable selections are `REVIEW_UNAVAILABLE`. Classify acceptance from actual
> families/completion/scope. Forward invocation reviewer/model/effort overrides
> to reviewer-bearing children. Generation workers are unchanged.


Write the patent specification based on: **$ARGUMENTS**

Adapted from `/paper-write` for patent specifications. The specification supports the claims -- it is not a paper.

## Constants

- `REVIEWER_MODEL = gpt-6-astra` — External reviewer for specification quality
- `JURISDICTION = "auto"` — Inherit from pipeline or detect from args; `CN`, `US`, `EP`, `ALL`
- `OUTPUT_FORMAT = "markdown"` — Markdown drafts; converted to filing format by `/jurisdiction-format`
- `OUTPUT_DIR = "patent/"` — Base output directory
- `LANGUAGE = "auto"` — Auto from jurisdiction: CN->Chinese, US/EP->English

## Inputs

1. `patent/CLAIMS.md` — the drafted claims (primary source)
2. `patent/INVENTION_DISCLOSURE.md` — invention decomposition
3. `patent/PRIOR_ART_REPORT.md` — for background section
4. User-provided figures (if any)

## Shared References

Load `../shared-references/patent-writing-principles.md` for specification writing rules, language guidelines, and reference numeral conventions.
Load `../shared-references/patent-format-cn.md` or `patent-format-us.md` or `patent-format-ep.md` based on jurisdiction.

## Workflow

### Step 1: Initialize Specification Structure

Create the output directory and section files:

```
patent/specification/
├── title.md
├── technical_field.md
├── background.md
├── summary.md
├── drawings_description.md
├── detailed_description.md
└── abstract.md
```

### Step 2: Write Title (Invent Name)

- Must match the broadest claim scope
- No trademarks, no "improved" or "new" or "novel"
- English format: "A [technical theme] method for [application area]" or "A [technical theme] device for [application area]."
- US/EP format: "[Technical topic] for [purpose]" or "[Technical topic] and method thereof"
- Keep concise (CN: typically under 25 characters; US: under 500 characters)

### Step 3: Write Technical Field (Technical areas)

1-2 paragraphs identifying the technical domain:
- "The present invention relates to [broad field], and more particularly to [specific area]."
- CN: "This invention involves...[Technical areas],Specific reference[Specific areas]。"

### Step 4: Write Background (Background technology)

This is NOT a literature review. It directly sets up the problem.

Structure:
1. Describe the closest prior art approaches (2-3 paragraphs)
2. Identify specific technical deficiencies of each approach
3. The deficiencies must be technical, not commercial or social
4. DO NOT admit the prior art is "superior" or "better"
5. DO NOT cite specific patent numbers unless they are known prior art (citations go in IDS for US, or Background section for CN)

CN format: "Background technology" section describing existing technology and its shortcomings.

### Step 5: Write Summary (Invent Contents)

Three parts, directly mirroring INVENTION_DISCLOSURE.md:

**Technical Problem (Technical problems to be solved)**:
- State the problem derived from background deficiencies
- CN: "The technical problem this invention has to solve...."

**Technical Solution (Technical programmes)**:
- Describe how the invention solves the problem
- Must provide support for ALL claim elements
- Start from the broadest claim and describe the core inventive concept
- CN: "In order to address the above-mentioned technology issues, the technology options used in this invention are:..."
- **NO formulas, NO mathematical derivations, NO circuit models** — these belong in Modalities of implementation, not Invent Contents

**Advantages (Useful effects)**:
- Benefits derived from the structural/technical features (qualitative reasoning)
- CN: "The beneficial effects of this invention are:..."
- **NO specific numerical results** (e.g., "detection limit 70μm", "response time 105ms") — these are experimental findings, not invention properties
- Frame advantages structurally: "As a result of the adoption...Structure, and therefore have...Effect"

### Step 6: Write Brief Description of Drawings (Annotations to the figure)

Invoke `/figure-description` as a sub-skill if user has provided figures:
```
/figure-description "patent/figures/"
```

If no user figures, describe what figures should exist based on the claims.

Format:
- CN: "Figure1Yes....schematic chart;2Yes....flowcharts;"
- US: "FIG. 1 is a block diagram showing...; FIG. 2 is a flowchart illustrating..."

### Step 7: Write Detailed Description (Modalities of implementation)

Invoke `/embodiment-description` as a sub-skill:
```
/embodiment-description "patent/CLAIMS.md"
```

This section must:
- Describe at least one complete embodiment with reference numerals
- Enable a POSITA to make and use the invention
- Support every claim element with explicit description
- Include variations and alternatives for broader claim interpretation

### Step 8: Write Abstract (Summary)

Jurisdiction-specific word limits:

| Jurisdiction | Word Limit | Notes |
|-------------|-----------|-------|
| CN | 300 words (Chinese characters) | Include most representative claim reference |
| US | 150 words (2500 characters) | Enable efficient searching, no legal phrases |
| EP | ~150 words | No statements on merits or value |

The abstract summarizes:
1. The technical field
2. The problem being solved
3. The technical solution (core features)
4. Key advantages

### Step 9: Claim Support Verification

Verify every claim element finds support in the specification:

| Claim | Element | Specification Section | Paragraph(s) | Reference Numeral |
|-------|---------|----------------------|-------------|-------------------|
| 1 | step a | detailed_description | ¶3 | 202 |
| 1 | step b | detailed_description | ¶4 | 204 |
| X | component A | detailed_description | ¶2 | 102 |

If any element lacks support, add the necessary description before proceeding.

### Step 10: Cross-Model Review

Call `REVIEWER_MODEL` via `mcp__codex__codex` with xhigh reasoning:

> Resolve this reviewer slot first; the following is the `backend=codex` example.

```
mcp__codex__codex:
  model: gpt-6-astra
  config: {"model_reasoning_effort": "xhigh"}
  prompt: |
    You are a patent examiner reviewing a specification for completeness.
    CLAIMS: [all claims]
    SPECIFICATION: [all specification sections]

    Check for:
    1. Written description support: Does every claim element have explicit or inherent support?
    2. Enablement: Can a POSITA practice the invention from this specification?
    3. Consistency: Do reference numerals match across figures and specification?
    4. Language quality: Any subjective terms, relative terms without definition, or result-to-be-achieved language?
    5. Missing embodiments: Are there claim features that need additional embodiments?
    6. Background deficiencies: Are they technical and specific enough?
```

### Step 11: Output

All specification sections are in `patent/specification/`.

Summary file: `patent/specification/SPECIFICATION_INDEX.md` with:
```markdown
## Patent Specification

### Sections
| Section | File | Word Count | Status |
|---------|------|-----------|--------|
| Title | title.md | | Complete |
| Technical Field | technical_field.md | | Complete |
| Background | background.md | | Complete |
| Summary | summary.md | | Complete |
| Drawings Description | drawings_description.md | | Complete |
| Detailed Description | detailed_description.md | | Complete |
| Abstract | abstract.md | | Complete |

### Claim Support Status
| Claim | Elements Supported | Elements Missing |
|-------|-------------------|-----------------|
| 1 | All | None |
| X | All | None |
```

## Key Rules

- The specification supports the claims, not the other way around. Every claim element must have support.
- Use consistent terminology -- same word for the same concept throughout.
- DO NOT include experimental results, accuracy metrics, or empirical evaluations.
- DO NOT use subjective language ("excellent", "surprising", "superior").
- Reference numerals must be consistent: same component, same numeral, everywhere.
- Background section describes specific deficiencies, not general "need for improvement."
- Multiple embodiments strengthen the specification but are not always required.
- Large file handling: if a Write operation fails, retry with Bash `cat <<'EOF'` heredoc.
- If the selected reviewer is unavailable, record `REVIEW_UNAVAILABLE`; continue only as an explicitly unreviewed draft, without switching providers.

## Mirror description (additional to this open warehouse)
- This document is considered upstream. ARIS mirrors in original;support files (scripts/、references/、../shared-references/)Not distributed with mirrors, full originals can be found at the upstream warehouse https://github.com/wanshuiyin/Auto-claude-code-research-in-sleep 。
- If supporting documents are cited for implementation skills, then the relative path should be parsed from the upstream warehouse.

Wersje

RepozytoriumWynikLicencja
Ta strona · jiangfeng-strathclyde/Athena100MIT
wanshuiyin/Auto-claude-code-research-in-sleep100MIT
wanshuiyin/Auto-claude-code-research-in-sleep100MIT
EpicenterHQ/epicenter100MIT

Migawka bazy z 13.11.2026 · wersja paczki f3ad1ea28575 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100claims-drafting
    Pisze zastrzeżenia patentowe dla wynalazku, czyli główny etap procesu patentowego.
  • 87patent-writer
    Wspiera pisanie chińskich zgłoszeń patentowych: wyszukiwanie patentów, dokument zgłoszenia wynalazku, wskazówki dotyczące procesu i strategii zgłoszeń.
  • 100patent-review
    Daje zewnętrzną recenzję zgłoszenia patentowego w stylu egzaminatora: uwagi do zastrzeżeń i opisu.
  • 100patent-assistant
    Pomaga zespołom R&D pisać zgłoszenia wynalazku, porządkować opis, wyszukiwać powiązane patenty i oceniać nowość.
  • 100claims-drafting
    Pisze zastrzeżenia patentowe dla wynalazku, jako podstawowy krok potoku patentowego.
  • 100claims-drafting
    Pisze zastrzeżenia patentowe dla wynalazku, jako podstawowy krok potoku patentowego.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.