# Openspec New Change

Start a new OpenSpec change using the experimental artifact workflow.

- Repository: https://github.com/fengshao1227/ccg-workflow (5956 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-21
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add fengshao1227/ccg-workflow --skill openspec-new-change -g -a claude-code -y`
Codex: `npx skills add fengshao1227/ccg-workflow --skill openspec-new-change -g -a codex -y`
Cursor: `npx skills add fengshao1227/ccg-workflow --skill openspec-new-change -g -a cursor -y`
Gemini CLI: `npx skills add fengshao1227/ccg-workflow --skill openspec-new-change -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add fengshao1227/ccg-workflow`

## 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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

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

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

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 (e.g., `proposal` for spec-driven).
   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.

6. **STOP and wait for user direction**

**Output**

The rest: https://github.com/fengshao1227/ccg-workflow/blob/HEAD/.agents/skills/openspec-new-change/SKILL.md