openspec-sync-specs

Merge delta OpenSpec specs into main specs using the OpenSpec CLI.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/aniwei/vitamin-code --skill openspec-sync-specs-aniwei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/aniwei/vitamin-code/tree/main/refs/opencode/.github/skills/openspec-sync-specs
Command: npx skills add https://github.com/aniwei/vitamin-code --skill openspec-sync-specs-aniwei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of syncing delta OpenSpec changes into the main spec repository, eliminating manual merge friction.

Core Features & Use Cases

  • Delta-to-main merge: Applies delta spec changes to the main specs automatically while preserving existing content.
  • Intelligent merging: Merges added, modified, removed, and renamed requirements with sensible defaults and prompts for ambiguity.
  • Guided workflow: Uses the OpenSpec CLI to enumerate changes, read delta specs, and update main specs safely.

Quick Start

Run the openspec-sync-specs command to merge delta specs into the main OpenSpec specs. The tool will prompt to select a change name if multiple delta specs exist, then apply changes.

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 OpenSpec changes into main specs?

To merge delta OpenSpec changes into main specs, run the openspec-sync-specs command. The tool automatically applies delta spec updates to the main repository while preserving existing content and enforcing intelligent merging rules.

How does OpenSpec handle syncing modified and renamed requirements?

Syncing modified and renamed requirements uses intelligent merging rules with sensible defaults to apply delta changes safely. The tool automatically processes ADDED, MODIFIED, REMOVED, and RENAMED requirements, prompting for input only when ambiguity exists.

Do I need the OpenSpec CLI to automate spec synchronization?

Yes, the OpenSpec CLI is required to automate spec synchronization. The tool uses the CLI to enumerate available changes, read delta specs, and safely update main specifications, ensuring guided workflow execution and idempotent updates.

What is the best way to apply multiple delta specs to an OpenSpec project?

The best way to apply multiple delta specs is running the sync command, which prompts you to select a specific change name. It then merges the chosen delta spec into the main OpenSpec specs automatically without manual merge friction.

Are OpenSpec spec updates idempotent when applying delta changes?

Yes, OpenSpec spec updates are idempotent when applying delta changes. The tool enforces intelligent merging rules that ensure applying the same delta spec multiple times yields the same final main specification state without duplicating content.