openspec-new-change

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

使用实验性的产出物驱动方法启动新变更。

输入：用户的请求应当包含变更名称（kebab-case）或对想要构建内容的描述。

步骤

如果没有提供明确的输入，询问用户想要构建什么

使用 AskUserQuestion Tool（开放式，无预设选项）询问：

"您想要处理什么变更？请描述您想要构建或修复的内容。"
根据他们的描述，推导出一个 kebab-case 名称（例如："add user authentication" →
```
add-user-auth
```
）。
重要提示：在不了解用户想要构建什么的情况下，请勿继续。
确定工作流 Schema
除非用户明确要求不同的工作流，否则使用默认 Schema（省略
```
--schema
```
）。
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
否则：省略
```
--schema
```
以使用默认值。
创建变更目录
bash
```
openspec-cn new change "<name>"
```
仅当用户请求特定工作流时才添加
```
--schema <name>
```
。这将在
```
openspec/changes/<name>/
```
下使用所选 Schema 创建一个脚手架变更。
显示产出物状态
bash
```
openspec-cn status --change "<name>"
```
这会显示哪些产出物需要创建，以及哪些已就绪（依赖项已满足）。
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".
bash
```
openspec-cn instructions <first-artifact-id> --change "<name>"
```
这会输出创建第一个产出物所需的模板和上下文。
停止并等待用户指示

输出

完成上述步骤后，进行总结：

变更名称和位置
正在使用的 Schema/工作流及其产出物顺序
当前状态（0/N 个产出物已完成）
第一个产出物的模板
提示："准备好创建第一个产出物了吗？请描述此变更的内容，我将为您起草，或者要求我继续。"

护栏

不要立即创建任何产出物 —— 仅显示指令
不要跳过显示第一个产出物模板的步骤
如果名称无效（非 kebab-case），请求有效的名称
如果同名变更已存在，建议继续处理该变更
如果使用非默认工作流，请传递 --schema

Launch a new change using an experimental artifact-driven approach.

Input: User requests should include the change name (kebab-case) or a description of what they want to build.

Steps

If no explicit input is provided, ask the user what they want to build

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

"What change do you want to work on? Please describe what you want to build or fix."
Derive a kebab-case name based on their description (e.g., "add user authentication" →
```
add-user-auth
```
).
Important Note: Do not proceed without understanding what the user wants to build.
Determine workflow Schema
Unless the user explicitly requests a different workflow, use the default Schema (omit
```
--schema
```
).
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 value.
Create change directory
bash
```
openspec-cn new change "<name>"
```
Add
```
--schema <name>
```
only if the user requests a specific workflow. This will create a scaffolded change under
```
openspec/changes/<name>/
```
using the selected Schema.
Display artifact status
bash
```
openspec-cn status --change "<name>"
```
This will show which artifacts need to be created and which are ready (dependencies are met).
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".
bash
```
openspec-cn instructions <first-artifact-id> --change "<name>"
```
This will output the templates and context required to create the first artifact.
Stop and wait for user instructions

Output

After completing the above steps, provide a summary:

Change name and location
Schema/workflow being used and its artifact order
Current status (0/N artifacts completed)
Template for the first artifact
Prompt: "Ready to create the first artifact? Please describe the content of this change, and I will draft it for you, or ask me to proceed."

Guardrails

Do not create any artifacts immediately — only display instructions
Do not skip the step of displaying the first artifact template
If the name is invalid (not kebab-case), request a valid name
If a change with the same name already exists, suggest continuing with that change
If using a non-default workflow, pass the --schema parameter