Openspec New Change

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.

3,306 stars 317 forksProductivity & Notes

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add rpamis/comet --skill openspec-new-change
Manual install
git clone --depth 1 https://github.com/rpamis/comet.git /tmp/comet
mkdir -p ~/.claude/skills
cp -r /tmp/comet/eval/local/skills/benchmarks/dependency/openspec/openspec-new-change ~/.claude/skills/openspec-new-change

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

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**
Read the full skill on GitHub

Details

Skill name
openspec-new-change
Repository
rpamis/comet
Path
eval/local/skills/benchmarks/dependency/openspec/openspec-new-change/SKILL.md
License
MIT
Repo updated
18 November 2026

FAQ

What does the Openspec New Change skill do?

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.

How do I install the Openspec New Change skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add rpamis/comet --skill openspec-new-change. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Openspec New Change popular?

It lives in rpamis/comet, which has 3,306 GitHub stars and 317 forks.

Related skills

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.