openspec-sync-specs

Merge delta spec changes into main OpenSpec specs idempotently.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/AdJIa/markdown-x --skill openspec-sync-specs-adjia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/AdJIa/markdown-x/tree/main/.cursor/skills/openspec-sync-specs
Command: npx skills add https://github.com/AdJIa/markdown-x --skill openspec-sync-specs-adjia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync delta specs from a change to main specs.

Core Features & Use Cases

  • Intelligent merging of delta changes into main specs while preserving existing content
  • Guardrails to prompt for ambiguous changes and ensure deterministic updates
  • End-to-end workflow: locate delta specs, merge into main specs, and create missing main specs when needed

Quick Start

Run the delta synchronization workflow by selecting a delta change and applying it to the main specs with the OpenSpec CLI.

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 using OpenSpec?

To merge delta specs into main specs, the synchronization workflow reads delta changes from openspec/changes and applies ADDED, MODIFIED, REMOVED, or RENAMED operations to update openspec/specs idempotently while preserving existing content.

What is the safest way to apply delta spec changes to main specs?

The safest way to apply delta spec changes is using an intelligent merging process that includes guardrails to prompt for ambiguous changes, ensuring deterministic updates to main specs without overwriting unintended content.

How does spec synchronization handle missing main specs during a merge?

Spec synchronization handles missing main specs by automatically creating them when needed, ensuring the end-to-end workflow from locating delta specs to merging changes completes successfully even if the target file does not yet exist.

Can I run delta synchronization idempotently with the OpenSpec CLI?

Yes, you can run delta synchronization idempotently with the OpenSpec CLI, meaning applying the same delta spec changes multiple times will consistently produce the same final main specs state without duplicating content.

What happens to existing content when syncing modified delta specs?

When syncing modified delta specs, the intelligent merging process preserves existing content in main specs, applying only the specific modifications defined in the delta while maintaining the original structure and information.

When should I use delta spec synchronization instead of manual merging?

You should use delta spec synchronization when you have delta specs under openspec/changes that need deterministic merging into openspec/specs, especially to avoid manual errors and ensure guardrails catch ambiguous modifications.