skills.rest
drakulavich
drakulavichCOMMUNITY
Explore all skills by this author →
𝕏@drakulavichGitHub

openspec-sync-specs

Merge delta spec changes into main specs while preserving unrelated content.

68|7|Updated Apr 6, 2026
Search Tags:#automation#repository#merge#spec#openspec#delta
One-click install
npx skills add https://github.com/drakulavich/kesha-voice-kit --skill openspec-sync-specs-drakulavich
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/drakulavich/kesha-voice-kit/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/drakulavich/kesha-voice-kit --skill openspec-sync-specs-drakulavich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs and main specs drift can cause conflicting changes and wasted effort. This Skill enables automated, safe synchronization by reading delta specs and merging them into the main specs while preserving existing content.

Core Features & Use Cases

  • Agent-driven delta merge: reads delta specs and updates the corresponding main specs with ADDED, MODIFIED, REMOVED, and RENAMED requirements.
  • Intelligent content preservation: retains content not mentioned in the delta and supports partial updates to minimize churn.
  • Create-on-miss workflow: creates a new main spec file when a capability does not exist yet.

Quick Start

Prompt the user to select a delta change and then merge delta specs into the main specs accordingly.

Frequently Asked Questions about openspec-sync-specs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync delta specs into main specs without losing existing content?▼

Syncing delta specs is achieved by reading the delta changes and applying ADDED, MODIFIED, REMOVED, and RENAMED requirements directly into the main specs. It preserves unrelated content to minimize churn and prevent data loss.

What happens if a main spec file is missing during a delta merge?▼

If a main spec file is missing during a delta merge, the Skill automatically creates a new main spec file. This create-on-miss workflow ensures that new capabilities are captured without interrupting the synchronization process.

Does the delta merge process require manual confirmation for critical changes?▼

Yes, the delta merge process requires explicit confirmation for critical changes. When requirements are ambiguous or involve major modifications, the Skill guides the user through interactive prompts before applying the updates to the main specs.

What is the best way to apply ADDED and REMOVED requirement changes to an OpenSpec repository?▼

The best way to apply ADDED and REMOVED requirement changes is to use an automated delta merge tool that reads OpenSpec delta specs and integrates them into the main specs. This ensures safe synchronization while retaining untouched repository content.

Can I use this automation to merge partial spec updates without causing massive file churn?▼

Yes, you can use this automation to merge partial spec updates because it supports intelligent content preservation. It only applies the specific modifications mentioned in the delta spec, leaving unrelated sections in the main specs completely untouched.

Related Skills

Explore More Software Engineering Skills→
jankneumannjankneumann
4

openspec-sync-specs

Merge delta spec changes into main OpenSpec specification files.

Community
Intermediate
estaciolimaestaciolima

speckit-git-commit

Automate Git staging and commits after Spec Kit lifecycle events.

Community
Intermediate
cynkracynkra
1

openspec-sync-specs

Merge delta OpenSpec requirement blocks into main spec files per capability.

Official
Intermediate
tungnguyen10tungnguyen10

openspec-sync-specs

Merge delta specification changes into main project spec files.

Community
Intermediate