What is openspec-new-change?

A workflow for starting a new OpenSpec change with structured documents for a feature, fix, or other modification.

It helps describe the work, create a change record, and begin the artifact-based planning process.

It gives an unclear software request a defined name and an organized path toward specifications and implementation.

openspec-new-change — Skill for Claude Code by intent-driven-dev

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add intent-driven-dev/openspec-schemas --skill openspec-new-change

Clone the repo

git clone --depth 1 https://github.com/intent-driven-dev/openspec-schemas

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/intent-driven-dev/openspec-schemas/openspec-new-change/github.svg)](https://agentmods.dev/skills/intent-driven-dev/openspec-schemas/openspec-new-change)

Your own site

<a href="https://agentmods.dev/skills/intent-driven-dev/openspec-schemas/openspec-new-change"><img src="https://agentmods.dev/badge/skills/intent-driven-dev/openspec-schemas/openspec-new-change/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/intent-driven-dev/openspec-schemas/openspec-new-change"><img src="https://agentmods.dev/badge/skills/intent-driven-dev/openspec-schemas/openspec-new-change.svg" alt="Reviewed on agentmods" width="80" 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 808 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 89% 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.00808
Opus 5.5	$0.00016	$0.00323
Sonnet 5.5	$0.00008	$0.00162
Haiku 4.5	$0.00004	$0.00081

Measured 1mo ago against content hash c993693c31bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-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 1mo 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

89% identical to openspec-new-change — 18 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 · 78 lines

What it actually says

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

Store selection: If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run openspec store list --json to discover registered store ids, then pass --store <id> on the commands that read or write specs and changes (new change, status, instructions, list, show, validate, archive, doctor, context). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local openspec/ root.

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 in the planning home resolved by the CLI.
Show the artifact status
```
openspec status --change "<name>" --json
```
Use the returned planningHome, changeRoot, artifactPaths, and nextSteps instead of assuming repo-local paths.
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.

1mo ago First seen · 78 lines · 40 tokens per session scan A c993693c31bc

Subscribe to this mod's changes

openspec-new-change is a skill published in the GitHub repository intent-driven-dev/openspec-schemas (110 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 808 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to openspec-new-change, differing in 18 lines, and is treated as a copy.

OpenSpec Planning Project management aicoding architectural-decision-records sdd spec-driven-development specdrivendevelopment

spec-manager

Spec-driven project iteration workflow: L1 PRD -> L2 Design -> L3 Impl -> Agent Task, with human review gates at each layer.

loki-ai-ch/spec-manager · 33 tokens

specd-archive-change

Encerra uma change do specd — confere gate verde, anuncia a escrita, aplica o delta em .specd/specs/ com specd archive e, havendo board, sincroniza e transiciona os itens da change. Use quando o usuário quiser finalizar, arquivar ou encerrar uma change já implementada.

jnerytech/specd · 76 tokens

specd-explore

Abre uma change do specd e explora o que ela vai encostar — escopo, mapa do código, requisitos existentes, lacunas — gravando o resultado em explore/notes.md e, havendo board, coletando o card com specd explore. Use quando o usuário quiser começar uma mudança, investigar antes de propor, ou entender o que já existe…

jnerytech/specd · 88 tokens

openspec-new-change