openspec-sync

Q: How do I install openspec-sync?

Run npx skills add https://github.com/full-stack-skills/openspec-skills --skill openspec-sync in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/openspec-sync/ (personal) or .claude/skills/openspec-sync/ (project).

by full-stack-skills

Sync delta specs from a change into main specs using /opsx:sync, without archiving the change. Use when the user says "sync specs", "merge specs to main", "/opsx:sync", or needs to update main specs mid-change.

Installs: 102
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/full-stack-skills/openspec-skills --skill openspec-sync

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads openspec-sync automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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/.

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

FAQ

What does the openspec-sync skill do?

How do I install openspec-sync?

Run npx skills add https://github.com/full-stack-skills/openspec-skills --skill openspec-sync in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/openspec-sync/ (personal) or .claude/skills/openspec-sync/ (project).

Which AI agents can use openspec-sync?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is openspec-sync safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains openspec-sync?

It is published by full-stack-skills in full-stack-skills/openspec-skills. It has 102 recorded installs.