openspec-sync-specs

Merge delta specification changes into main specification documents.

Updated Mar 8, 2026

Search Tags:#requirements #merge #sync #openspec #delta #specs

Ready to run

npx skills add https://github.com/deicer/codex-lb --skill openspec-sync-specs-deicer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/deicer/codex-lb/tree/main/.agents/skills/openspec-sync-specs
Command: npx skills add https://github.com/deicer/codex-lb --skill openspec-sync-specs-deicer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of updating main specification documents with changes defined in delta specification files, ensuring consistency and efficient management of evolving requirements.

Core Features & Use Cases

Intelligent Merging: Applies changes from delta specs (added, modified, removed, renamed requirements) to main specs intelligently, preserving existing content.
Capability-based Updates: Updates specifications on a per-capability basis.
Use Case: A product team has defined new requirements in a delta spec for a specific feature. This Skill applies those new requirements to the main specification document without requiring manual copy-pasting or complex merging.

Quick Start

Use the openspec-sync-specs skill to sync changes from the 'feature-enhancement' change to 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 specification documents?▼

To merge delta specs into main specification documents, you synchronize the additions, modifications, removals, and renames of requirements on a per-capability basis. This process updates main specs automatically without manual copy-pasting.

What are delta specs used for in software requirements management?▼

Delta specs are used to define specific changes to evolving software requirements. They capture additions, modifications, removals, and renames, which are then synchronized into main specification documents to maintain consistency across capabilities.

Do I need the openspec CLI to sync delta specs?▼

Yes, you need the openspec CLI to sync delta specs. The synchronizer requires the CLI for listing and applying changes to maintain specification integrity during the intelligent merge process.

How do I apply changes from a feature enhancement to main specs without manual copy-pasting?▼

You apply changes from a feature enhancement to main specs by using a synchronization skill to intelligently merge the delta specification files. This automatically preserves existing content while applying the defined requirement changes.

What is the best way to update main specs on a per-capability basis?▼

The best way to update main specs on a per-capability basis is to use an automated synchronization tool that intelligently merges delta specification files. This ensures only the targeted capabilities receive the requirement changes.

Why does syncing requirements preserve existing content in main specs?▼

Syncing requirements preserves existing content in main specs because the intelligent merge process applies only the defined additions, modifications, removals, and renames from delta specs. This prevents overwriting previously established specification details.