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.
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
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.
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:
--schema <name>openspec schemas --jsonOtherwise: Omit --schema to use the default.
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.
Show the artifact status
openspec status --change "<name>"
This shows which artifacts need to be created and which are ready (dependencies satisfied).
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.
STOP and wait for user direction
Output
After completing the steps, summarize:
Guardrails
Before reporting completion for any task in this repository (OpenSpec or non-OpenSpec), explicitly run and report this gate:
AGENTS.md and .junie/guidelines.md are authoritative and non-overridable.docs/contracts/ currency/sync check executed (including no-diff cases).docs/contracts/** and related CHANGELOG.md files.docs/governance/scope-CHANGELOG.md.docs/backlog/iteration-*.json and python3 scripts/backlog_render.py executed.sbt test and pre-commit run --all-files.If an item is not applicable, mark it as N/A with a short reason. Do not silently skip gate items.