openspec-sync-specs

Merge delta specs into main specs for ADDED, MODIFIED, REMOVED, and RENAMED changes.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/ssd-mkdocs-platform/teams-board --skill openspec-sync-specs-ssd-mkdocs-platform
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/ssd-mkdocs-platform/teams-board/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/ssd-mkdocs-platform/teams-board --skill openspec-sync-specs-ssd-mkdocs-platform

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync delta specs into a change-to-main-specs workflow, enabling incremental updates without archiving.

Core Features & Use Cases

  • Delta-driven synchronization: read delta specs from openspec/changes and apply to main specs, supporting ADDED, MODIFIED, REMOVED, and RENAMED sections.
  • Intelligent merging: preserves existing content not mentioned in delta, and merges changes deterministically.
  • Safe execution: idempotent and transparent, summarizing updates after each run.

Quick Start

Provide the change name to merge, and the system will apply delta specs into the corresponding main specs while preserving existing 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 archiving?

The merge process handles ADDED, MODIFIED, REMOVED, and RENAMED sections deterministically. It reads delta specs from openspec/changes and applies them to openspec/specs, preserving existing content and creating new specs when missing.

What changes are supported when syncing delta specs?

Syncing delta specs supports ADDED, MODIFIED, REMOVED, and RENAMED section changes. The process applies these incremental updates deterministically while preserving existing main spec content not mentioned in the delta.

Do I need the openspec CLI to sync delta specs?

Yes, the openspec CLI is required to sync delta specs. It handles reading delta specs from openspec/changes and merging them into openspec/specs deterministically while preserving existing content.

Is merging delta specs idempotent?

Yes, merging delta specs is idempotent. Running the merge multiple times produces the same result, preserving existing content and summarizing updates transparently after each run without duplicating changes.

What happens to main spec content not mentioned in a delta spec?

Content not mentioned in the delta spec is preserved. The merge process only applies ADDED, MODIFIED, REMOVED, and RENAMED changes from the delta, leaving existing untouched content in the main specs intact.

How do I create new specs if they are missing during a delta merge?

The system creates new specs automatically when they are missing during a delta merge. Provide the change name, and the process will apply delta specs into openspec/specs, creating new specs when missing while preserving existing content.