openspec-sync-specs

Merge delta specs into main specs with guided change selection.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW --skill openspec-sync-specs-inspedralbes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW/tree/main/prj-entrades-nou/.cursor/skills/openspec-sync-specs
Command: npx skills add https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW --skill openspec-sync-specs-inspedralbes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync delta specs from a change to main specs. This action enables intelligent merging where delta specs are applied to main specs, avoiding wholesale changes and enabling targeted updates such as adding a new scenario without duplicating the entire requirement.

Core Features & Use Cases

  • Agent-driven merging: read delta specs and directly edit main specs to apply changes, enabling intelligent merging (e.g., adding a scenario without copying the entire requirement).
  • Delta discovery and application: locate delta specs under openspec/changes/<name>/specs and apply them to the corresponding main specs, creating main specs when missing.
  • Robust merge semantics: support ADDED, MODIFIED, REMOVED, and RENAMED operations with guidance to preserve content not mentioned in the delta.
  • Guided prompts: prompt for a change name when ambiguous and show available changes before applying updates.

Quick Start

Provide the delta change name when prompted and allow the agent to merge delta specs into 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 overwriting existing requirements?

Delta spec merging applies targeted changes using ADDED, MODIFIED, REMOVED, and RENAMED operations while preserving main spec content not mentioned in the delta, avoiding wholesale overwrites and enabling updates like adding a single scenario.

What is an agent-driven spec merge workflow?

Agent-driven merging reads delta specs from openspec/changes and directly edits corresponding main specs to apply changes intelligently, creating missing main specs automatically and supporting guided prompts when the change name is ambiguous.

How do I apply delta specs when the main spec file is missing?

When applying delta specs, the merge process automatically creates missing main specs during synchronization, as delta discovery locates specs under openspec/changes/<name>/specs and generates the corresponding main spec files.

Does the openspec merge process support REMOVED and RENAMED operations?

The openspec merge process supports ADDED, MODIFIED, REMOVED, and RENAMED operations with robust merge semantics, providing guidance to preserve existing main spec content not explicitly mentioned in the delta change.

What happens if multiple delta changes exist and I don't specify which one to merge?

When the change name is ambiguous, guided prompts ask you to select a specific change, showing available changes found under openspec/changes before applying any delta spec updates to main specs.

When should I avoid using automated spec synchronization for merging changes?

Avoid automated spec synchronization when you need to restructure entire requirements rather than apply targeted updates, as the merge process is designed for incremental delta application, preserving unmentioned content rather than wholesale rewrites.