What is openspec-new-change?

A guided workflow for starting a new OpenSpec change, such as a feature, bug fix, or other code modification. OpenSpec is a tool for managing planned changes through structured work steps.

Use it when you want to start an OpenSpec change from a request or description.

It gives a new change a name and creates the files needed to track its work.

How wangjs-jacky/quick-ai configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to wangjs-jacky/quick-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/wangjs-jacky/quick-ai/main/.claude/skills/openspec-new-change/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/wangjs-jacky/quick-ai

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/wangjs-jacky/quick-ai/openspec-new-change.svg)](https://agentmods.dev/skills/wangjs-jacky/quick-ai/openspec-new-change)

Your own site

<a href="https://agentmods.dev/skills/wangjs-jacky/quick-ai/openspec-new-change"><img src="https://agentmods.dev/badge/skills/wangjs-jacky/quick-ai/openspec-new-change.svg" alt="Measured on agentmods" height="20"></a>

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 658 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 80% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00040	$0.00658
Opus 5	$0.00020	$0.00329
Sonnet 5	$0.00008	$0.00132
Haiku 4.5	$0.00004	$0.00066

Measured 7d ago against content hash 7a9e54256eba, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

openspec-new-change scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

80% identical to openspec-new-change — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/openspec-new-change/SKILL.md · 75 lines

What it actually says

Start a new change using the experimental artifact-driven approach.

Input: The user's request should include a change name (kebab-case) OR a description of what they want to build.

Steps

If no clear input provided, ask what they want to build

Use the AskUserQuestion tool (open-ended, no preset options) to ask:

"What change do you want to work on? Describe what you want to build or fix."

From their description, derive a kebab-case name (e.g., "add user authentication" → add-user-auth).

IMPORTANT: Do NOT proceed without understanding what the user wants to build.
Determine the workflow schema

Use the default schema (omit --schema) unless the user explicitly requests a different workflow.

Use a different schema only if the user mentions:
- A specific schema name → use --schema <name>
- "show workflows" or "what workflows" → run openspec schemas --json and let them choose
Otherwise: Omit --schema to use the default.
Create the change directory
```
openspec new change "<name>"
```
Add --schema <name> only if the user requested a specific workflow. This creates a scaffolded change at openspec/changes/<name>/ with the selected schema.
Show the artifact status
```
openspec status --change "<name>"
```
This shows which artifacts need to be created and which are ready (dependencies satisfied).
Get instructions for the first artifact The first artifact depends on the schema (e.g., proposal for spec-driven). Check the status output to find the first artifact with status "ready".
```
openspec instructions <first-artifact-id> --change "<name>"
```
This outputs the template and context for creating the first artifact.
STOP and wait for user direction

Output

After completing the steps, summarize:

Change name and location
Schema/workflow being used and its artifact sequence
Current status (0/N artifacts complete)
The template for the first artifact
Prompt: "Ready to create the first artifact? Just describe what this change is about and I'll draft it, or ask me to continue."

Guardrails

Do NOT create any artifacts yet - just show the instructions
Do NOT advance beyond showing the first artifact template
If the name is invalid (not kebab-case), ask for a valid name
If a change with that name already exists, suggest continuing that change instead
Pass --schema if using a non-default workflow

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

7d ago First seen · 75 lines · 40 tokens per session scan A 7a9e54256eba

Subscribe to this mod's changes

openspec-new-change is a skill published in the GitHub repository wangjs-jacky/quick-ai (5 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 658 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 80% identical to openspec-new-change, differing in 12 lines, and is treated as a copy.

Claude Code Planning Project management ai-coding developer-tools opencode vscode vscode-extension

gh-issues

Use when creating, triaging, or commenting on GitHub issues for the Kilo VS Code extension or JetBrains plugin via gh. Covers issue templates, project board assignment, title conventions, and required gh scopes.

Kilo-Org/kilocode · 50 tokens

icon-jetbrains

Create or review IntelliJ New UI SVG icons, theme variants, sizes, and palette.

Kilo-Org/kilocode · 23 tokens

vscode-visual-regression

Write Storybook stories and visual regression tests for the Kilo VS Code extension webview UI.

Kilo-Org/kilocode · 25 tokens

release-jetbrains

Use when releasing the Kilo JetBrains plugin -- resolve a version ("next rc" or explicit), run the prepare workflow, edit and commit a filtered human-readable changelog on the release PR, then watch publish to completion.

Kilo-Org/kilocode · 50 tokens

kilocode-merge-minimizer

Use when changing shared upstream-owned files to add Kilo-specific behavior, editing kilocodechange markers in shared code, or moving additive behavior out of shared code to reduce upstream merge conflicts. Do not use for changes confined to Kilo-owned paths such as packages/kilo-vscode/ or packages/kilo-ui/.

Kilo-Org/kilocode · 76 tokens

chart

Use when the user asks to visualize data with charts, graphs, or plots using the chart tool (bar, line, scatter, pie, time series, etc.).

Kilo-Org/kilocode · 37 tokens

quick-ai: Skill for Claude Code