openspec-sync-specs

Merge delta spec changes into main specification files.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/rafazafar/codex-octopus --skill openspec-sync-specs-rafazafar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/rafazafar/codex-octopus/tree/main/.agents/skills/openspec-sync-specs
Command: npx skills add https://github.com/rafazafar/codex-octopus --skill openspec-sync-specs-rafazafar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync delta specs from a change to main specs.

Core Features & Use Cases

  • Intelligent delta-merge: reads delta specs and applies changes to the main spec with idempotent merging.
  • Guided collaboration: prompts for selection when multiple changes exist and preserves existing content not mentioned in delta.
  • Auto-create main specs: creates main spec files if they don't exist and applies the added requirements.

Quick Start

Run the sync agent to merge a selected delta spec 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?

To merge delta specs safely, this automation reads changes from openspec/changes and applies ADDED, MODIFIED, REMOVED, and RENAMED requirements through intelligent merging, preserving unrelated content in the main specification.

Can I automatically create missing main spec files when syncing delta specs?

Yes, syncing delta specs can auto-create missing main spec files on demand. When a main specification does not exist, the tool creates it and applies the added requirements from the delta spec automatically.

How does spec management handle multiple delta specs waiting to be applied?

When multiple delta specs exist, the sync process prompts for change selection. This guided collaboration ensures you choose which specific delta spec under openspec/changes to merge into the corresponding main specs.

What is the best way to apply idempotent merging for OpenSpec changes?

The best way to apply idempotent merging is using a dedicated sync agent that reads delta spec files and applies changes to the main spec, ensuring repeated merges do not duplicate or overwrite unrelated requirements.

Does delta spec synchronization support RENAMED and REMOVED requirements?

Yes, delta spec synchronization supports RENAMED and REMOVED requirements. It reads these changes from the delta spec and applies them to the main specification alongside ADDED and MODIFIED requirements.

When should I not use automated spec merging for my changes?

You should not use automated spec merging if your changes require manual review of unrelated content, as the tool preserves existing content not mentioned in the delta spec and only applies explicitly defined requirement changes.