Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fengshao1227/openspec-verify-change
Verify implementation matches change artifacts.
Passed 12 of 16 test cases with the skill, and 8 of 16 without it.
and 6 more in the full report
8 fixed8 passed either way3 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
When running the initial change lookup using openspec list --json for a user who didn't specify a change name, which subset of changes should be presented for user selection?
| Checked | Without skill | With skill |
|---|---|---|
| Filters user selection to changes that possess implementation tasks. | Missed | Passed |
| Marks changes with incomplete tasks with an In Progress indicator. | Missed | Passed |
The instructions your model reads when the skill loads.
Verify that an implementation matches the change artifacts (specs, tasks, design).
Input: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
Steps
If no change name provided, prompt for selection
Run openspec list --json to get available changes. Use the AskUserQuestion tool to let the user select.
Show changes that have implementation tasks (tasks artifact exists). Include the schema used for each change if available. Mark changes with incomplete tasks as "(In Progress)".
IMPORTANT: Do NOT guess or auto-select a change. Always let the user choose.
Check status to understand the schema
openspec status --change "<name>" --json
Parse the JSON to understand:
schemaName: The workflow being used (e.g., "spec-driven")Get the change directory and load artifacts
openspec instructions apply --change "<name>" --json
This returns the change directory and context files. Read all available artifacts from contextFiles.
Initialize verification report structure
Create a report structure with three dimensions:
Each dimension can have CRITICAL, WARNING, or SUGGESTION issues.
test cases passed, vs 8 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.