openspec-sync-specs

Merge delta specs into main specs with idempotent updates.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/SynthropicTechnology/diegobarbosa-os --skill openspec-sync-specs-synthropictechnology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/SynthropicTechnology/diegobarbosa-os/tree/main/.cursor/skills/openspec-sync-specs
Command: npx skills add https://github.com/SynthropicTechnology/diegobarbosa-os --skill openspec-sync-specs-synthropictechnology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs are proposals to modify main specifications. This skill merges those delta specs into the matching main specs while preserving existing content and provenance, enabling controlled, incremental updates.

Core Features & Use Cases

  • Intelligent merging: applies ADDED, MODIFIED, REMOVED, and RENAMED requirements to the correct main spec without overwriting unrelated content.
  • Scope-aware updates: updates only touched capabilities and creates main specs when missing.
  • Safe guardrails: prompts for change selection when multiple deltas exist and ensures idempotent results.

Quick Start

Run the openspec-sync-specs tool to merge delta specs into the main specs.

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 specs into main specs without overwriting existing content?

Merging delta specs into main specs applies ADDED, MODIFIED, REMOVED, and RENAMED requirements to the correct main spec while preserving unrelated content and provenance for controlled, incremental updates.

What happens when a capability spec does not exist yet during a delta spec merge?

When a capability does not exist yet, the merge process creates a new main spec file automatically under openspec/specs/<capability>/spec.md to establish the baseline specification.

How does intelligent merging handle multiple delta specs in openspec/changes?

Intelligent merging satisfies guardrails by prompting for change selection when multiple deltas exist, ensuring idempotent updates that only touch affected capabilities.

Can I apply REMOVED and RENAMED requirements to existing main specs safely?

Applying REMOVED and RENAMED requirements modifies main specs safely by targeting specific entries without overwriting unrelated content, maintaining spec integrity across updates.

What is the best way to apply incremental specification changes from delta files?

The best way to apply incremental specification changes is using scope-aware merging that updates only touched capabilities and ensures idempotent results across delta files.

Does merging delta specs affect unrelated content in the main spec file?

Merging delta specs preserves unrelated content in the main spec file, applying changes only to the specific requirements defined in the delta while keeping existing content intact.