skills.rest
Yager-42
Yager-42COMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-sync-specs

Merge delta specifications into primary OpenSpec specs while preserving unrelated content.

Updated Dec 26, 2025
Search Tags:#automation#merge#openspec#delta-specs#spec-management#change-propagation
One-click install
npx skills add https://github.com/Yager-42/-- --skill openspec-sync-specs-yager-42
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/Yager-42/--/tree/main/.codex/skills/openspec-sync-specs
Command: npx skills add https://github.com/Yager-42/-- --skill openspec-sync-specs-yager-42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync delta specs from delta changes into main specs to keep the source of truth updated without archiving the delta.

Core Features & Use Cases

  • Intelligent delta merging across specs: ADDED, MODIFIED, REMOVED, and RENAMED requirements are applied to main specs while preserving unrelated content.
  • User-guided change selection: prompts you to pick the delta change when multiple are available.
  • On-demand main spec creation: creates openspec/specs/<capability>/spec.md if a capability has delta updates but no main spec yet.

Quick Start

Proceed to merge the delta specs into the corresponding main specs by selecting a change when prompted and applying the delta changes 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 without archiving the delta changes?▼

Merging delta specifications intelligently applies ADDED, MODIFIED, REMOVED, and RENAMED requirements to main specs while preserving unrelated existing content in the target files.

What is the best way to propagate ADDED, MODIFIED, and REMOVED requirements from a delta change?▼

Merging delta specifications intelligently applies ADDED, MODIFIED, REMOVED, and RENAMED requirements to main specs while preserving unrelated existing content in the target files.

How do I select which delta change to apply when multiple changes exist in openspec?▼

Applying delta changes automatically creates a new main spec file at openspec/specs/<capability>/spec.md when the capability has delta updates but no existing main spec yet.

Can I automatically create a new main spec if a capability only has delta specifications?▼

Applying delta changes automatically creates a new main spec file at openspec/specs/<capability>/spec.md when the capability has delta updates but no existing main spec yet.

How do I apply RENAMED requirements to the primary specification set without losing existing content?▼

The openspec delta merge handles multiple capabilities and delta specs located under openspec/changes/<name>/specs, applying each change to the corresponding main specification.

Does the openspec merge workflow support delta specs across multiple capabilities at once?▼

The openspec delta merge handles multiple capabilities and delta specs located under openspec/changes/<name>/specs, applying each change to the corresponding main specification.

Related Skills

Explore More Software Engineering Skills→
kunishkunish

openspec-sync-specs

Merge delta specs into main OpenSpec specs with idempotent rules.

Community
Advanced
linaproailinaproai
147

openspec-archive-change

Archive completed OpenSpec workflow changes to dated directories with completion validation.

Official
Intermediate
MarcialFantiniMarcialFantini

sdd-spec

Generate delta specs documenting added, modified, and removed requirements with RFC 2119 keywords.

Community
Advanced
crozzbitecrozzbite

openspec-sync-specs

Merge delta specs into main specs using the openspec CLI.

Community
Advanced