openspec-sync-specs

Merge Openspec delta requirements into main specs preserving untouched content and prompting ambiguity resolution.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/dentedgem9846-claw/chronocrystal-opsx --skill openspec-sync-specs-dentedgem9846-claw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/dentedgem9846-claw/chronocrystal-opsx/tree/main/.pi/skills/openspec-sync-specs
Command: npx skills add https://github.com/dentedgem9846-claw/chronocrystal-opsx --skill openspec-sync-specs-dentedgem9846-claw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs often diverge from main specs and require careful integration to preserve existing content while applying new changes. This Skill automates safe merging of delta changes into main specs through structured ADDED, MODIFIED, REMOVED, and RENAMED handling, reducing manual effort and errors.

Core Features & Use Cases

  • Intelligent delta merging: apply ADDED/MODIFIED/REMOVED/RENAMED requirements to main specs while preserving unrelated content.
  • Change-aware synchronization: locate delta specs under openspec/changes/<name>/specs and apply them to corresponding main specs in an idempotent manner.
  • Guardrails and prompts: prompt for ambiguous changes and preserve existing content not mentioned in the delta.
  • Use case: merge a delta that adds a new requirement and modifies an existing one without recreating the entire main spec.

Quick Start

Provide the delta change name and run the openspec sync command 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 losing existing requirements?

Delta specs represent incremental changes—such as ADDED, MODIFIED, REMOVED, or RENAMED requirements—that must be integrated into main specs without recreating the entire document, preserving unrelated content while enacting targeted updates.

What is the best way to synchronize openspec delta changes idempotently?

Yes, the merge process preserves content not mentioned in the delta spec and includes guardrails to avoid overwriting existing successful configurations, ensuring only explicitly targeted requirements are updated during synchronization.

How to apply ADDED and MODIFIED requirements to openspec main specs?

Provide the delta change name and run the openspec sync command to intelligently merge delta specs into main specs, applying ADDED and MODIFIED requirements while maintaining the coherence of the overall specification document.

What happens when ambiguous delta changes are found during spec synchronization?

When ambiguous changes are detected during synchronization, the workflow pauses and prompts the user for clarification, ensuring that uncertain modifications are not applied blindly and protecting the integrity of the main specs.