openspec-sync-specs

Merge delta specs from openspec/changes into openspec/specs with ADDED, MODIFIED, REMOVED, and RENAMED changes.

19|4|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/ZanebonoAlter/Syntopica --skill openspec-sync-specs-zanebonoalter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/ZanebonoAlter/Syntopica/tree/main/.opencode/skills/openspec-sync-specs
Command: npx skills add https://github.com/ZanebonoAlter/Syntopica --skill openspec-sync-specs-zanebonoalter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync delta specs from a change to main specs.

Core Features & Use Cases

  • Automates intelligent merging of delta specs into the main specification set.
  • Supports ADDED, MODIFIED, REMOVED, and RENAMED transformations with guided prompts to avoid mis-merging.
  • Creates new main specs automatically if they don't exist, preserving existing content where not overridden.

Quick Start

Tell the agent to read delta specs from openspec/changes and merge them into openspec/specs, prompting for a change name when needed.

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 automatically?▼

Syncing delta specs applies ADDED, MODIFIED, REMOVED, and RENAMED changes from openspec/changes into openspec/specs. It preserves existing main spec content unless explicitly overridden, creating new main specs automatically when needed.

What is the best way to sync openspec changes without losing existing spec content?▼

Syncing delta specs applies ADDED, MODIFIED, REMOVED, and RENAMED changes from openspec/changes into openspec/specs. It preserves existing main spec content unless explicitly overridden, creating new main specs automatically when needed.

How do I handle multiple delta specs during an agent-driven merge?▼

During an agent-driven merge, the workflow prompts you for the specific change name when multiple delta specs exist. This ensures the correct delta spec is applied to the main specs without mis-merging.

Do I need to manually create new main specs before merging openspec changes?▼

No, you do not need to manually create new main specs. The merge workflow automatically creates new main specifications in openspec/specs if they do not already exist before applying the delta changes.

What happens to main specs content when it is not overridden by a delta spec?▼

Existing main specs content is fully preserved when not overridden by a delta spec. The intelligent merge only applies the specified ADDED, MODIFIED, REMOVED, or RENAMED changes, leaving the rest of the document intact.