openspec-sync
OpenSpec Sync Skill
Use /opsx:sync to merge delta specs from a change into the main openspec/specs/ directory without archiving the change. The change remains active after sync. This is optional — openspec-archive handles syncing automatically when archiving.
When to Use
- Long-running change where the user wants specs in main before archiving.
- Multiple parallel changes need updated base specs.
- The user wants to review/preview the merge separately before archiving.
Prerequisites
- An active change with delta specs in
specs/.
Workflow
-
Run sync
/opsx:sync— sync the current/inferred change./opsx:sync <change-name>— sync a specific change.
-
What happens
- Reads delta specs from the change folder.
- Parses ADDED / MODIFIED / REMOVED sections.
- Merges changes into
openspec/specs/. - Preserves existing content not mentioned in the delta.
- The change remains active (not archived).
-
Verify
- Review the updated specs in
openspec/specs/.
- Review the updated specs in
Outputs
- Updated
openspec/specs/with delta changes merged. - Change remains active in
openspec/changes/<name>/.
Next Steps
- Continue working on the change, or use openspec-archive when done.
Troubleshooting
- "No delta specs": The change has no
specs/directory; create specs via openspec-continue or openspec-ff first. - Conflicts with other changes: Sync handles merging at the requirement level; if two changes modify the same requirement, the latest sync wins.
References
More from partme-ai/openspec-skills
openspec-explore
Think through ideas, investigate problems, and clarify requirements before committing to a change using `/opsx:explore`. Use when the user says "explore an idea", "think through this", "investigate options", or wants to brainstorm before creating a formal change.
50openspec-apply
Implement tasks from the change using `/opsx:apply`, working through the task list and checking off items. Use when the user says "implement", "apply the change", "/opsx:apply", or "start coding from tasks".
40openspec-schema
Create and manage custom workflow schemas using `openspec schema init/fork/validate/which`. Use when the user says "create a custom workflow", "custom schema", "fork a schema", or wants to define their own artifact types and dependencies.
35openspec-archive
Archive a completed change with `/opsx:archive`, merging delta specs into main specs and preserving the change for history. Use when the user says "archive the change", "finish up", "/opsx:archive", or "mark this change as done".
35openspec-new
Start a new OpenSpec change with `/opsx:new`, creating a change folder with metadata and scaffolding. Use when the user says "start a new change", "new feature", "/opsx:new", or "create an OpenSpec change".
29openspec-ff
Fast-forward through artifact creation with `/opsx:ff`, generating all planning artifacts (proposal, specs, design, tasks) at once. Use when the user says "fast forward", "create all artifacts", "/opsx:ff", or has a clear picture of what to build.
24