openspec-sync-specs

Merge delta specifications into main OpenSpec repository specs.

Updated Mar 9, 2025
One-click install
npx skills add https://github.com/rock-hu/vitamin-compose --skill openspec-sync-specs-rock-hu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/rock-hu/vitamin-compose/tree/main/.qwen/skills/openspec-sync-specs
Command: npx skills add https://github.com/rock-hu/vitamin-compose --skill openspec-sync-specs-rock-hu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill synchronizes delta specifications into the main Openspec repository, enabling updates from a delta spec to be merged into the master specs.

Core Features & Use Cases

  • Agent-driven delta merging: reads delta specs and applies changes to main specs while preserving existing content.
  • Intelligent change application: handles ADDED, MODIFIED, REMOVED, and RENAMED changes with idempotent behavior.
  • Automated delta discovery: locates delta specs under openspec/changes/<name>/specs/... and updates the corresponding main specs, creating them if needed.
  • Safe review workflow: preserves content not mentioned in the delta and prompts for clarification when delta is ambiguous.
  • Use Case: When a delta introduces a new requirement, merge it as a new added requirement without overwriting existing scenarios.

Quick Start

Run the delta merge flow on a change with the openspec tool.

  • List available delta changes: openspec list --json
  • Select a change and run the merge to apply delta specs to the main specs
  • Review the updated main specs to verify changes and preserve non-delta content

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?

To merge delta specs into main specs without losing content, apply the delta changes intelligently by reading ADDED, MODIFIED, REMOVED, and RENAMED operations while preserving existing main spec content not mentioned in the delta.

What is an idempotent spec merge in OpenSpec?

An idempotent spec merge in OpenSpec applies delta specifications to main specs repeatedly without causing duplicate changes, ensuring the final main spec state remains identical regardless of how many times the merge runs.

How do I apply ADDED and REMOVED changes to a main spec?

You apply ADDED and REMOVED changes by reading the delta spec from openspec/changes/<name>/specs/... and executing the specified operations against the main spec, creating the main spec file if it does not already exist.

Does the delta merge process prompt for clarification when changes are ambiguous?

Yes, the delta merge process prompts for clarification when any delta specification is unclear or ambiguous, ensuring safe review workflows and preventing unintended modifications to the main OpenSpec repository.

Can I automatically create main specs if they do not exist during a merge?

Yes, you can automatically create main specs when they do not exist by applying the delta spec changes, which will generate the corresponding main spec files in the OpenSpec repository during the synchronization process.