Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ayrtonvwf/openspec-archive-change
Archive a completed change in the experimental workflow.
Passed 3 of 9 test cases with the skill, and 3 of 9 without it.
and 1 more in the full report
4 fixed4 passed either way11 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
The user simply asks 'Archive my change' without specifying a change name or context. What command is executed first to find available active changes?
| Checked | Without skill | With skill |
|---|---|---|
| Executes openspec list --json to list active changes. | Missed | Passed |
The instructions your model reads when the skill loads.
Archive a completed change in the experimental workflow.
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 only active changes (not already archived). Include the schema used for each change if available.
IMPORTANT: Do NOT guess or auto-select a change. Always let the user choose.
Check artifact completion status
Run openspec status --change "<name>" --json to check artifact completion.
Parse the JSON to understand:
schemaName: The workflow being usedplanningHome, changeRoot, artifactPaths, and actionContext: path and scope contextartifacts: List of artifacts with their status (done or other)If status reports actionContext.mode: "workspace-planning", explain that workspace archive is not supported in this slice and STOP. Do not move workspace changes into repo-local archives or edit linked repos.
If any artifacts are not done:
Check task completion status
Read the tasks file (typically tasks.md) to check for incomplete tasks.
Count tasks marked with - [ ] (incomplete) vs - [x] (complete).
If incomplete tasks found:
test cases passed, vs 3 / 9 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.