Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fengshao1227/openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow.
1 of 22 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 1 comparable cases; this report requires 8.
A test case the skill fixed. Same model, same prompt, with and without the skill.
After creating a change `fix-cors-policy` in OpenSpec, what exact command inspects which artifacts are ready or pending?
| Checked | Without skill | With skill |
|---|---|---|
| uses `openspec status --change "fix-cors-policy"` to check artifact state | Missed | Passed |
The instructions your model reads when the skill loads.
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 --json and let them chooseOtherwise: 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).
test cases passed with the skill
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.