skills.rest
zh-impact
zh-impactCOMMUNITY
Explore all skills by this author →
GitHub

openspec-sync-specs

Merge delta specs into main specs with idempotent conflict-aware handling.

Updated Aug 23, 2026
Search Tags:#automation#merge#idempotent#openspec#delta#specs
One-click install
npx skills add https://github.com/zh-impact/fcollections --skill openspec-sync-specs-zh-impact
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/zh-impact/fcollections/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/zh-impact/fcollections --skill openspec-sync-specs-zh-impact

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merge delta specs into main specs to keep them in sync.

Core Features & Use Cases

  • Intelligent delta-merging: reads delta specs and applies changes to main specs with conflict-aware handling.
  • Guided operations: prompts for change selection when multiple deltas exist and preserves unrelated content.
  • Robust handling of ADDED, MODIFIED, REMOVED, and RENAMED requirements with idempotent behavior.

Quick Start

Run the openspec CLI to select a delta and apply its changes 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 specs into main specs to keep them in sync?▼

Delta specs are merged into main specs by applying ADDED, MODIFIED, REMOVED, and RENAMED changes across multiple capabilities. The merge validates deltas, preserves unrelated content, and operates idempotently to keep everything in sync.

What happens when merging delta specs with ambiguous changes?▼

When ambiguous changes exist during delta merging, the process prompts for change selection. This guided operation ensures you choose the correct delta to apply while preserving unrelated content in the main specs.

Can I apply delta changes across multiple capabilities idempotently?▼

Yes, delta changes are applied across multiple capabilities with idempotent behavior. This means running the merge multiple times produces the same result, ensuring main specs stay synchronized without duplicating applied changes.

What types of requirement changes are supported when syncing delta specs?▼

Syncing delta specs supports ADDED, MODIFIED, REMOVED, and RENAMED requirement changes. The merge intelligently handles these delta types to update main specs while preserving unrelated content.

How do I select and apply a specific delta to main specs?▼

You can select a specific delta and apply its changes to corresponding main specs using the openspec CLI. This guides the operation by prompting for selection when multiple deltas exist.

Does merging delta specs preserve unrelated content in main specs?▼

Yes, merging delta specs preserves unrelated content in main specs. The intelligent delta-merge only applies ADDED, MODIFIED, REMOVED, and RENAMED changes while leaving all other existing content untouched.

Related Skills

Explore More Software Engineering Skills→
SQDR2SQDR2

openspec-sync-specs

Merge delta specifications into main specs by applying ADDED, MODIFIED, REMOVED, and RENAMED blocks.

Community
Advanced
psaccpsacc

openspec-sync-specs

Merge delta specification changes into main openspec spec files.

Community
Advanced
JanuaryLabsJanuaryLabs
4

openspec-archive-change

Archive completed openspec changes after verifying artifacts and syncing delta specs.

Official
Advanced
remiverdiesenremiverdiesen
6

openspec-sync-specs

Merge delta specification changes into main spec files with an idempotent summary.

Community
Intermediate