openspec-sync-specs

Merge delta specs into main OpenSpec specification files.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/anaclumos/verifidia --skill openspec-sync-specs-anaclumos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/anaclumos/verifidia/tree/main/.opencode/skills/openspec-sync-specs
Command: npx skills add https://github.com/anaclumos/verifidia --skill openspec-sync-specs-anaclumos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs often sit separately from the main specification baseline. This skill merges delta specifications into the primary specs to apply changes without archiving or losing context, supporting intelligent, incremental updates.

Core Features & Use Cases

  • Intelligent merging: apply ADDED, MODIFIED, REMOVED, and RENAMED changes with content preservation.
  • Automated conflict handling: preserves existing content not mentioned by the delta and prompts when ambiguous.
  • Use Case: maintain main specs by merging multiple deltas from openspec/changes/<change>/specs into openspec/specs.

Quick Start

Run the merge tool to apply delta specs from openspec/changes/<change>/specs into the main openspec/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 losing existing content?

You can merge delta specs into main specs by running the automation tool to apply changes from openspec/changes/ to openspec/specs. It processes ADDED, MODIFIED, REMOVED, and RENAMED requirements while preserving existing content not mentioned by the delta.

What is the best way to apply incremental specification updates to a baseline?

Applying incremental specification updates to a baseline is best handled by merging delta specs into the primary specs. This approach automatically processes added, modified, removed, and renamed requirements while preserving existing content not mentioned by the delta.

Can I use openspec-sync-specs to handle renamed requirements in delta specs?

Yes, openspec-sync-specs handles renamed requirements in delta specs. It automatically applies RENAMED changes from delta specifications organized under openspec/changes/<name>/specs to the corresponding main specs under openspec/specs.

Does merging delta specs into main specs create the main spec if it is missing?

Yes, merging delta specs into main specs creates the main specification file if it is missing. When applying changes from the delta, the tool initializes the corresponding main spec under openspec/specs and populates it with the new requirements.

What happens to main spec content that is not mentioned in the delta spec?

Content in the main spec not mentioned in the delta spec is preserved during the merge. The tool only applies explicit ADDED, MODIFIED, REMOVED, and RENAMED changes from the delta, ensuring existing baseline context is not lost.

How does the merge tool report changes after applying delta specs?

After applying delta specs, the merge tool reports a summary of changes. This summary details the added, modified, removed, and renamed requirements applied from openspec/changes/<name>/specs into the main openspec/specs baseline.