Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ayrtonvwf/openspec-propose
Propose a new change with all artifacts generated in one step.
Passed 9 of 18 test cases with the skill, and 4 of 18 without it.
and 7 more in the full report
10 fixed2 passed either way9 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
Before composing the content for the `proposal` artifact of `stripe-billing`, what exact CLI command and options fetch its schema rules and template in machine-readable format?
| Checked | Without skill | With skill |
|---|---|---|
| Executes openspec instructions proposal --change stripe-billing --json. | Missed | Passed |
The instructions your model reads when the skill loads.
Propose a new change - create the change and generate all artifacts in one step.
I'll create a change with artifacts:
When ready to implement, run /opsx:apply
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.
Create the change directory
openspec new change "<name>"
This creates a scaffolded change in the planning home resolved by the CLI with .openspec.yaml.
Get the artifact build order
openspec status --change "<name>" --json
Parse the JSON to get:
test cases passed, vs 4 / 18 without
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.