**Mode Configuration**: This prompt runs in non-interactive environments (e.g., CI/CD, automation scripts).

**Non-Interactive Mode Behavior**:
- DO NOT use `AskUserQuestion` or any interactive tools
- When user input is required, use reasonable defaults (e.g., select the most recently modified change)
- Skip optional confirmation steps, document assumptions made

**Interactive Mode Behavior**:
- Follow the normal interactive flow with user prompts

---

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

{{#if changeDescription}}
**Change Description**: {{ changeDescription }}
{{/if}}

{{#if changeName}}
**Change Name**: {{ changeName }}
{{/if}}

{{#if hasTargetRepositories}}
**Target Repositories**: This change is scoped to the following repositories:
{{#each targetRepositories}}
- `{{ this.Path }}` ({{ this.Name }})
{{/each}}
All file operations, code changes, and artifact generation should be confined to these repository paths.
{{/if}}

**Steps**

1. **If no input provided, use reasonable defaults**

   If `changeDescription` or `changeName` is provided in the input context, use it.

   **In non-interactive mode**:
   - Document the assumption: "No input provided, using default behavior"
   - Continue waiting for user to provide the change description or name

   **In interactive mode**:
   - Ask the user: "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.

2. **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.

3. **Create the change directory**
   ```bash
   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.

4. **Show the artifact status**
   ```bash
   openspec status --change "<name>"
   ```
   This shows which artifacts need to be created and which are ready (dependencies satisfied).

5. **Get instructions for the first artifact**
   The first artifact depends on the schema. Check the status output to find the first artifact with status "ready".
   ```bash
   openspec instructions <first-artifact-id> --change "<name>"
   ```
   This outputs the template and context for creating the first artifact.

**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? Run `/opsx:continue` or just describe what this change is about and I'll draft it."

**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 using `/opsx:continue` instead
- Pass --schema if using a non-default workflow
{{#if hasTargetRepositories}}
- **IMPORTANT**: All file operations must be within the specified target repositories
{{/if}}
