openspec-sync-specs

Merge delta specs into main OpenSpec specification files.

5|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/Catsofsuffering/CCGS --skill openspec-sync-specs-catsofsuffering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/Catsofsuffering/CCGS/tree/main/.agents/skills/openspec-sync-specs
Command: npx skills add https://github.com/Catsofsuffering/CCGS --skill openspec-sync-specs-catsofsuffering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the tedious and error-prone task of applying delta specification changes from a change package into the main OpenSpec repository, ensuring incremental edits are merged intelligently without wholesale replacements or accidental loss of unrelated content.

Core Features & Use Cases

  • Safe, intelligent merging: Read ADDED, MODIFIED, REMOVED, and RENAMED sections in delta specs and apply targeted updates to main specs.
  • Create missing capabilities: Automatically create new capability spec files when a delta introduces a new capability.
  • User-driven selection and guardrails: Prompt users to select the change to apply, preserve unrelated content, show summaries of edits, and aim for idempotent operations.
  • Use Case: A spec author wants to propagate a change package that adds scenarios to an existing requirement and renames another requirement without overwriting hand-edited content.

Quick Start

Run the openspec-sync-specs skill and select the change to apply so delta specs are merged 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 OpenSpec specification files?

To merge delta specs into main OpenSpec specification files, you apply targeted updates from a change package by parsing ADDED, MODIFIED, REMOVED, and RENAMED sections to intelligently merge edits without wholesale replacements.

What is a delta spec in OpenSpec and when do I need to sync it?

A delta spec in OpenSpec captures incremental requirement changes within a change package. You need to sync it when authors add, modify, remove, or rename requirements across capabilities and want those changes propagated into main specs.

Does merging OpenSpec change packages preserve unrelated hand-edited content?

Merging OpenSpec change packages preserves unrelated hand-edited content through idempotent intelligent merges that apply targeted updates to main specs, ensuring no accidental loss of existing requirements or manually edited sections.

Do I need the openspec CLI to apply changes from a change package?

Yes, you need the openspec CLI to list and read changes stored under openspec/changes/<name>/specs, which the sync process parses to apply ADDED, MODIFIED, REMOVED, and RENAMED sections into main specification files.

Can I automatically create new capability spec files when syncing delta specs?

Yes, you can automatically create new capability spec files when a delta introduces a new capability, allowing the sync process to generate the missing files while applying the rest of the change package updates.

What are the limitations of syncing delta specs for OpenSpec repositories?

Syncing delta specs is limited to OpenSpec repositories where delta specs are stored under openspec/changes/<name>/specs, requiring the openspec CLI to list and read changes before performing the intelligent merge.