1---2name: openspec-new-change3description: 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.4license: MIT5compatibility: Requires openspec CLI.6metadata:7 author: openspec8 version: "1.0"9 generatedBy: "1.4.1"10---1112Start a new change using the experimental artifact-driven approach.1314**Input**: The user's request should include a change name (kebab-case) OR a description of what they want to build.1516**Steps**17181. **If no clear input provided, ask what they want to build**1920 Use the **AskUserQuestion tool** (open-ended, no preset options) to ask:21 > "What change do you want to work on? Describe what you want to build or fix."2223 From their description, derive a kebab-case name (e.g., "add user authentication" → `add-user-auth`).2425 **IMPORTANT**: Do NOT proceed without understanding what the user wants to build.26272. **Determine the workflow schema**2829 Use the default schema (omit `--schema`) unless the user explicitly requests a different workflow.3031 **Use a different schema only if the user mentions:**32 - A specific schema name → use `--schema <name>`33 - "show workflows" or "what workflows" → run `openspec schemas --json` and let them choose3435 **Otherwise**: Omit `--schema` to use the default.36373. **Create the change directory**38 ```bash39 openspec new change "<name>"40 ```41 Add `--schema <name>` only if the user requested a specific workflow.42 This creates a scaffolded change in the planning home resolved by the CLI.43444. **Show the artifact status**45 ```bash46 openspec status --change "<name>" --json47 ```48 Use the returned `planningHome`, `changeRoot`, `artifactPaths`, and `nextSteps` instead of assuming repo-local paths.49505. **Get instructions for the first artifact**51 The first artifact depends on the schema (e.g., `proposal` for spec-driven).52 Check the status output to find the first artifact with status "ready".53 ```bash54 openspec instructions <first-artifact-id> --change "<name>"55 ```56 This outputs the template and context for creating the first artifact.57586. **STOP and wait for user direction**5960**Output**6162After completing the steps, summarize:63- Change name and location64- Schema/workflow being used and its artifact sequence65- Current status (0/N artifacts complete)66- The template for the first artifact67- Prompt: "Ready to create the first artifact? Just describe what this change is about and I'll draft it, or ask me to continue."6869**Guardrails**70- Do NOT create any artifacts yet - just show the instructions71- Do NOT advance beyond showing the first artifact template72- If the name is invalid (not kebab-case), ask for a valid name73- If a change with that name already exists, suggest continuing that change instead74- Pass --schema if using a non-default workflow