mcpField
O
openspec-sync

openspec-sync

github.com/partme-aiDevelopment35 installs
Repository

About openspec-sync

openspec-sync is a skill for merging a change’s delta specs into the main OpenSpec specs directory without archiving the change. It is intended for active or parallel changes when the updated base specs need review before the change is archived.

Key features

  1. 01Merge delta specs into openspec/specs/
  2. 02Handle ADDED, MODIFIED, and REMOVED sections
  3. 03Preserve content not specified in the delta
  4. 04Keep the change active after syncing
  5. 05Resolve requirement conflicts with the latest sync

Use cases

  1. 01Update base specs during a long-running change
  2. 02Make updated specs available to parallel changes
  3. 03Review a spec merge before archiving

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/partme-ai/openspec-skills --skill openspec-sync

After installing, type/openspec-syncin Claude Code to confirm it loaded.

Details

From the project README

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

  1. Run sync

    • /opsx:sync — sync the current/inferred change.
    • /opsx:sync <change-name> — sync a specific change.

  2. 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).

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

Comments

Markdown supported