openspec-new-change

Agent Skills › jingsewu/open-wes › openspec-new-change

openspec-new-change

GitHub

用于启动新的 OpenSpec 变更。引导用户输入需求，确定工作流模式，创建变更目录并展示初始工件模板。全程仅生成脚手架和指令，不实际创建内容，等待用户确认后继续。

.claude/skills/openspec-new-change/SKILL.md jingsewu/open-wes

Trigger Scenarios

用户想要创建新功能、修复或修改用户提到使用结构化步骤进行开发用户希望开始新的 OpenSpec 变更

Install

npx skills add jingsewu/open-wes --skill openspec-new-change -g -y

More Options

Non-standard path

npx skills add https://github.com/jingsewu/open-wes/tree/master/.claude/skills/openspec-new-change -g -y

Use without installing

npx skills use jingsewu/open-wes@openspec-new-change

指定 Agent (Claude Code)

npx skills add jingsewu/open-wes --skill openspec-new-change -a claude-code -g -y

安装 repo 全部 skill

npx skills add jingsewu/open-wes --all -g -y

预览 repo 内 skill

npx skills add jingsewu/open-wes --list

SKILL.md

Frontmatter

{
    "name": "openspec-new-change",
    "license": "MIT",
    "metadata": {
        "author": "openspec",
        "version": "1.0",
        "generatedBy": "1.2.0"
    },
    "description": "Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.",
    "compatibility": "Requires openspec CLI."
}

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