openspec-sync-specs

Merge delta specs into main specs with idempotent updates.

Updated Dec 31, 2025
One-click install
npx skills add https://github.com/rockdong/stock_for_cpp --skill openspec-sync-specs-rockdong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/rockdong/stock_for_cpp/tree/main/.opencode/skills/openspec-sync-specs
Command: npx skills add https://github.com/rockdong/stock_for_cpp --skill openspec-sync-specs-rockdong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs often diverge from main specs, creating inconsistency. This skill provides a safe, automated way to merge changes from delta specs into the primary specifications without archiving or losing the change context, ensuring the main specs stay up to date.

Core Features & Use Cases

  • Intelligent delta-to-main merging: combines ADDED, MODIFIED, REMOVED, and RENAMED requirements into the primary specs while preserving existing content.
  • Guarded updates: performs idempotent operations, prompts when changes are ambiguous, and preserves user intent.
  • Use Case: when a delta spec introduces a small improvement to a capability, merge it into main specs and keep the delta for traceability.

Quick Start

Run the delta-spec merge workflow to apply delta specifications to main specs with intelligent merging.

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 content?

Delta specs merge into main specs by applying ADDED, MODIFIED, REMOVED, and RENAMED sections intelligently, preserving existing content while keeping the delta for traceability. This ensures main specs stay up to date without archiving.

What is the best way to apply incremental spec updates across multiple capabilities?

Incremental spec updates are applied by reading delta specs and integrating them into main specs using idempotent operations. This safe merging process supports multiple capabilities and preserves user intent when changes are ambiguous.

Does OpenSpec support idempotent updates for spec management?

OpenSpec spec management supports idempotent updates through guarded delta-spec merging. The workflow performs safe, automated operations that can be repeated without causing data inconsistency or losing the change context.

How do I handle ADDED, MODIFIED, REMOVED, and RENAMED requirements when merging specifications?

Handling these requirements involves reading the delta spec format and combining each section into the primary specs. The merging process preserves existing content and prompts when updates are ambiguous to guard user intent.

Why do my delta specs diverge from main specs and how can I fix it?

Delta specs diverge from main specs due to unmerged incremental changes. Fix this by running an automated delta-to-main merge workflow that safely integrates updates while preserving the delta spec for historical traceability.

Can I keep my delta spec for traceability after merging it into the primary specification?

You can keep the delta spec for traceability after merging. The intelligent merging process applies changes to main specs without archiving or deleting the original delta, ensuring the change context is always preserved.