openspec-sync-specs

Apply delta specifications to update or create main OpenSpec files.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/guillaumejay/FileIndexer --skill openspec-sync-specs-guillaumejay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/guillaumejay/FileIndexer/tree/main/.gemini/skills/openspec-sync-specs
Command: npx skills add https://github.com/guillaumejay/FileIndexer --skill openspec-sync-specs-guillaumejay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merges delta specifications into the main specification set to keep OpenSpec projects synchronized, reducing manual merge toil and drift.

Core Features & Use Cases

  • Intelligent merging of ADDED, MODIFIED, REMOVED, and RENAMED requirements based on delta specs.
  • Reads delta specifications from openspec/changes and updates or creates main specs accordingly.
  • Preserves existing content in main specs and provides guardrails for ambiguity or conflicts to ensure safe application.

Quick Start

Provide the delta change name and the agent will merge delta specs into the 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 in an OpenSpec workflow?

To merge delta specs into main specs, provide the delta change name so the tool can read from openspec/changes and apply ADDED, MODIFIED, REMOVED, and RENAMED requirements to update the primary specification set.

What is delta specification synchronization and when do I need it?

Delta specification synchronization consolidates change specifications into the main spec set. You need it to keep OpenSpec projects synchronized and reduce manual merge toil and specification drift.

How do I apply ADDED, MODIFIED, and REMOVED requirements to existing specifications?

You apply requirement changes by running a merge process that reads delta specs and intelligently updates or creates main specs, preserving existing content while providing guardrails for ambiguity or conflicts.

Can I synchronize OpenSpec changes without losing existing content in main specs?

Yes, synchronizing OpenSpec changes preserves existing content in main specs by intelligently applying only the delta changes and providing guardrails to prompt you when ambiguity or conflicts arise during the merge.

What happens when there are conflicts or ambiguity during delta spec merging?

When ambiguity or conflicts occur during delta spec merging, the process provides guardrails and prompts to ensure safe application, preventing automated overwrites of existing main specification content.

Does OpenSpec spec synchronization handle RENAMED requirements automatically?

Yes, OpenSpec synchronization handles RENAMED requirements automatically as part of its intelligent merging process, alongside ADDED, MODIFIED, and REMOVED requirements, to update capabilities across the main specification set.