openspec-sync-specs

Name: openspec-sync-specs
Availability: InStock
Author: cenmiao

Merge delta spec changes into main specification files.

Updated Mar 31, 2026

Search Tags:#cli #merge #idempotent #sync #openspec #specs #delta-specs

Ready to run

npx skills add https://github.com/cenmiao/openspec-pro --skill openspec-sync-specs-cenmiao

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/cenmiao/openspec-pro/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/cenmiao/openspec-pro --skill openspec-sync-specs-cenmiao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates merging changes from delta specification files into the repository's main specification files, removing the need for manual, error-prone edits and enabling targeted, partial updates.

Core Features & Use Cases

Intelligent merging: Apply ADDED, MODIFIED, REMOVED, and RENAMED requirement edits from delta specs into main specs while preserving content not mentioned in the delta.
Per-capability updates and creation: Read delta specs under openspec/changes/<name>/specs/<capability>/spec.md and update or create openspec/specs/<capability>/spec.md as needed.
User-driven selection and summaries: Prompt the user to select a change, validate delta spec presence, perform idempotent edits, and provide a clear summary of added, modified, removed, and renamed requirements.

Quick Start

Select the change that contains delta specs and run the skill to apply those deltas 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 specs idempotently?▼

To merge delta specs into main specs idempotently, apply changes from openspec/changes/<name>/specs into openspec/specs. This process reads both files and applies ADDED, MODIFIED, REMOVED, and RENAMED edits while preserving unmentioned content.

How does intelligent spec synchronization handle unmentioned requirements?▼

Intelligent spec synchronization preserves unmentioned requirements by reading both delta and main spec files during the merge. It specifically applies targeted ADDED, MODIFIED, REMOVED, and RENAMED edits without overwriting existing content not referenced in the delta.

What is the best way to automate ADDED, MODIFIED, and REMOVED requirement edits?▼

The best way to automate ADDED, MODIFIED, and REMOVED requirement edits is using an intelligent merge skill. It reads delta spec files under openspec/changes/<name>/specs/<capability>/spec.md and applies them to main specs automatically during release workflows.

Can I create new main specification files from delta specs?▼

Yes, you can create new main specification files from delta specs. The merge process reads delta specs under openspec/changes/<name>/specs/<capability>/spec.md and automatically creates the corresponding openspec/specs/<capability>/spec.md file when necessary.

Does spec merging work for per-capability updates during release workflows?▼

Spec merging works for per-capability updates during release workflows by targeting specific capability directories. It reads delta specs for each capability and applies the changes directly to update or create the matching main specification files.

Why do I need idempotent merges for spec maintenance?▼

You need idempotent merges for spec maintenance to ensure repeated applications of the same delta spec do not cause duplicate or conflicting edits. This guarantees safe, consistent updates to main specification files during automated release workflows.