Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ayrtonvwf/openspec-sync-specs
Sync delta specs from a change to main specs.
Passed 7 of 13 test cases with the skill, and 5 of 13 without it.
3 fixed8 passed either way10 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
When syncing change 'profile-settings', should we search the entire repository filesystem using find or git status to locate spec markdown files, or rely on CLI metadata?
| Checked | Without skill | With skill |
|---|---|---|
| Uses artifactPaths.specs.existingOutputPaths from the openspec status JSON output to locate delta spec files. | Missed | Passed |
The instructions your model reads when the skill loads.
Sync delta specs from a change to main specs.
This is an agent-driven operation - you will read delta specs and directly edit main specs to apply the changes. This allows intelligent merging (e.g., adding a scenario without copying the entire requirement).
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 delta specs (under specs/ directory).
IMPORTANT: Do NOT guess or auto-select a change. Always let the user choose.
Resolve change context
Run:
openspec status --change "<name>" --json
If status reports actionContext.mode: "workspace-planning", explain that workspace spec sync is not supported in this slice and STOP. Do not fall back to repo-local paths or edit linked repos.
Find delta specs
Use artifactPaths.specs.existingOutputPaths from the status JSON as the list of delta spec files.
Each delta spec file contains sections like:
## ADDED Requirements - New requirements to add## MODIFIED Requirements - Changes to existing requirements## REMOVED Requirements - Requirements to remove## RENAMED Requirements - Requirements to rename (FROM:/TO: format)If no delta specs found, inform user and stop.
For each delta spec, apply changes to main specs
test cases passed, vs 5 / 13 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.