openspec-sync-specs

Merge delta specifications into main spec files while preserving unrelated content.

Updated Dec 8, 2025
One-click install
npx skills add https://github.com/open-platform-model/cli --skill openspec-sync-specs-open-platform-model
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/open-platform-model/cli/tree/main/.opencode/skills/openspec-sync-specs
Command: npx skills add https://github.com/open-platform-model/cli --skill openspec-sync-specs-open-platform-model

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs can diverge from the main specs as changes accumulate. This skill provides a guided, intelligent merge workflow to synchronize delta updates into the canonical specs without overwriting unrelated content.

Core Features & Use Cases

  • Intelligent delta-to-main merging that preserves unrelated content while applying new or modified requirements.
  • Supports ADDED, MODIFIED, REMOVED, and RENAMED delta operations with idempotent behavior.
  • Creates main spec files on-demand if missing and generates a summary of changes for auditing.

Quick Start

Run the openspec-sync-specs tool to merge delta specs into 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 unrelated content?

The merge process handles ADDED, MODIFIED, REMOVED, and RENAMED delta operations with idempotent behavior. It applies these changes to delta specs located under openspec/changes/<change-name>/specs/*/spec.md, updating or creating the corresponding main spec files.

What is delta spec synchronization in openspec?

This synchronization updates or creates openspec/specs/<capability>/spec.md files as needed. It produces a summary detailing added, modified, removed, and renamed requirements for full auditability and traceability.

Can main spec files be created on-demand during the delta merging process?

Yes, main spec files can be created on-demand during the delta merging process. If a target specification does not exist, the merge workflow creates the necessary openspec/specs/<capability>/spec.md file automatically to apply the delta changes.

How do I track added, modified, and removed requirements after merging specifications?

You track added, modified, and removed requirements after merging specifications by reviewing the generated change summary. The merge workflow produces an audit summary detailing all applied delta operations for traceability and compliance verification.

Does the openspec delta merge overwrite existing canonical specs?

No, the openspec delta merge does not overwrite existing canonical specs. It intelligently applies delta updates while preserving unrelated content, ensuring that only the specified requirements are added, modified, removed, or renamed in the primary set.