openspec-sync-specs

Merge delta specs into main specs within the openspec workflow.

273|270|Updated Jun 30, 2025
One-click install
npx skills add https://github.com/LIDR-academy/AI4Devs-LTI-extended --skill openspec-sync-specs-lidr-academy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/LIDR-academy/AI4Devs-LTI-extended/tree/main/.cursor/skills/openspec-sync-specs
Command: npx skills add https://github.com/LIDR-academy/AI4Devs-LTI-extended --skill openspec-sync-specs-lidr-academy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specifications describe incremental changes; merging them into the main specs ensures synchronization and traceability without archiving changes.

Core Features & Use Cases

  • Intelligent delta merging: reads delta specs and updates the corresponding main specs, preserving unrelated content.
  • Creates missing main specs when needed and handles ADDED, MODIFIED, REMOVED, and RENAMED changes.
  • Idempotent operation: repeated execution yields the same result and maintains data integrity.

Quick Start

Run the openspec tool to merge delta specs into the corresponding 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 losing existing content?

Merging delta specs into main specs requires an intelligent tool that applies incremental changes while preserving unrelated content. It reads delta files and synchronizes only targeted modifications to ensure traceability without archiving changes.

What is a delta spec in version control and when do I need to merge it?

A delta spec describes incremental changes in version control. You need to merge it into main specs when synchronizing updates from openspec/changes to openspec/specs to maintain a single source of truth for your documentation.

Can I automate synchronizing ADDED, MODIFIED, and REMOVED changes in openspec?

Yes, you can automate synchronizing ADDED, MODIFIED, REMOVED, and RENAMED changes in openspec. The automation intelligently updates main specs, creates missing files when needed, and operates idempotently for safe repeated executions.

Does idempotent spec merging prevent data duplication when applied multiple times?

Idempotent spec merging prevents data duplication by ensuring repeated execution yields the same result and maintains data integrity. Running the merge operation multiple times will not create duplicate content or alter the final state.

What is the best way to handle RENAMED changes when merging openspec documentation?

The best way to handle RENAMED changes during openspec documentation merging is using an intelligent delta sync tool. It automatically processes RENAMED modifications alongside ADDED, MODIFIED, and REMOVED entries to update main specs smoothly.