openspec-sync-specs

Merge delta specification changes into main capability specs.

2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/yandiaan/penginfo-handal-hackathon --skill openspec-sync-specs-yandiaan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/yandiaan/penginfo-handal-hackathon/tree/main/.qoder/skills/openspec-sync-specs
Command: npx skills add https://github.com/yandiaan/penginfo-handal-hackathon --skill openspec-sync-specs-yandiaan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs often diverge from main specs; this Skill provides a safe, intelligent way to merge delta changes into main specifications without archiving changes.

Core Features & Use Cases

  • Intelligent merging across ADDED, MODIFIED, REMOVED, and RENAMED sections.
  • Preserves existing content not mentioned in the delta and supports idempotent runs.
  • Creates new main specs when a capability doesn't exist, applying delta-driven updates.

Quick Start

Specify a delta change name and run the openspec-sync-specs workflow to apply its delta specs to the corresponding 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 specifications into main specs without losing existing content?

To merge delta specifications into main specs safely, this workflow scans delta folders under openspec/changes, applies ADDED, MODIFIED, REMOVED, and RENAMED sections, and preserves all existing content not explicitly mentioned in the delta changes.

What is the best way to synchronize openspec delta changes into main capability specifications?

Synchronizing openspec delta changes is best handled by applying delta-driven updates to main capability specs, which automatically creates new main specs when a capability doesn't exist and ensures idempotent results with a clear summary.

Can I apply delta spec changes to main specs that do not exist yet?

Yes, applying delta spec changes to non-existent main specs is fully supported; the synchronization process automatically creates new main capability specs when needed and applies the delta-driven updates directly to them.

Does merging openspec delta specs support idempotent runs?

Yes, merging openspec delta specs supports idempotent runs, meaning you can apply the same delta changes multiple times without causing duplication or unintended side effects, always producing a clear synchronization summary.

What happens to main spec content that is not mentioned in the delta changes?

Main spec content not mentioned in the delta changes is safely preserved during the merge process, ensuring the synchronization only modifies the target specification based on the ADDED, MODIFIED, REMOVED, and RENAMED sections.