openspec-sync-specs

Merge delta specs into main specs under openspec/specs without archiving.

1|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/woutervanranst/Arius7 --skill openspec-sync-specs-woutervanranst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/woutervanranst/Arius7/tree/main/.opencode/skills/openspec-sync-specs
Command: npx skills add https://github.com/woutervanranst/Arius7 --skill openspec-sync-specs-woutervanranst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs are often developed separately and then need to be merged back into the main specification set. This skill provides an agent-driven workflow to synchronize those changes directly into the main specs without archiving the delta, enabling intelligent merging.

Core Features & Use Cases

  • Reads delta specs from openspec/changes/<name>/specs and merges them into the corresponding main specs under openspec/specs.
  • Creates new main spec files when a capability does not exist yet, with a brief purpose and the added requirements.
  • Preserves unrelated content and applies delta intent without wholesale replacement, supporting added/modified/renamed/removal guidance.

Quick Start

Run the openspec sync to merge delta specs into the main specification set.

Frequently Asked Questions about openspec-sync-specs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I merge delta specifications into main specs without losing existing content?

To merge delta specifications into main specs without losing content, identify changes under openspec/changes and update corresponding files under openspec/specs. The skill preserves existing content not mentioned in the delta and applies the delta intent intelligently.

What is the best way to synchronize multiple delta specs across different capabilities?

Synchronizing multiple delta specs across capabilities involves reading each delta under openspec/changes/<name>/specs and updating or creating the corresponding main specs under openspec/specs, applying added, modified, renamed, or removal guidance as needed.

Can I create new main spec files automatically when a capability does not exist yet?

Yes, you can create new main spec files automatically when a capability does not exist. The synchronization process creates a new main spec file under openspec/specs with a brief purpose and the added requirements from the delta.

Does merging delta specs archive the original delta files?

No, merging delta specs does not archive the original delta files. The process synchronizes changes directly into the main specification set without archiving the delta, enabling an intelligent merge workflow.

What happens when the delta spec merge encounters unclear or conflicting changes?

When the delta spec merge encounters unclear or conflicting changes, the process fails safe by prompting for clarification. This ensures that ambiguous modifications are resolved before updating the main specifications.