Openspec New Change
- 12 installs
- 28.2k repo stars
- Updated August 1, 2026
- alibaba/druid
openspec-new-change is a Claude skill that starts a new OpenSpec change with a structured, step-by-step artifact workflow.
About
openspec-new-change starts a new OpenSpec change using a structured, step-by-step artifact workflow. A developer uses it when they want to create a feature or fix and walk through each artifact deliberately rather than all at once. It creates the change directory, shows artifact status, and displays the first artifact's template before stopping for user direction.
- Starts a new OpenSpec change with the experimental artifact-driven workflow
- Creates the change directory and shows the first artifact template
- Stops after the first artifact so the developer directs each step
Openspec New Change by the numbers
- 12 all-time installs (skills.sh)
- Ranked #2,163 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
What openspec-new-change says it does
Start a new change using the experimental artifact-driven approach.
Do NOT advance beyond showing the first artifact template
npx skills add https://github.com/alibaba/druid --skill openspec-new-changeAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 12 |
|---|---|
| repo stars | ★ 28.2k |
| Last updated | August 1, 2026 |
| Repository | alibaba/druid ↗ |
What it does
Start a new OpenSpec change and step through its artifacts one at a time.
Who is it for?
Beginning an OpenSpec change deliberately, one artifact at a time.
Skip if: Generating all artifacts in one pass (use the fast-forward variant).
When should I use this skill?
When the user wants to start a new feature or fix as an OpenSpec change and step through artifacts.
What you get
A new change directory with the first artifact template ready to fill in.
Files
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 --jsonand let them choose
Otherwise: Omit --schema to use the default.
3. Create the change directory
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
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".
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
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? Just describe what this change is about and I'll draft it, or ask me to continue."
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 continuing that change instead
- Pass --schema if using a non-default workflow
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493k