openspec-sync-specs

Merge delta spec changes into main OpenSpec specification files.

4|1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/jankneumann/agentic-coding-tools --skill openspec-sync-specs-jankneumann
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/jankneumann/agentic-coding-tools/tree/main/.agents/skills/openspec-sync-specs
Command: npx skills add https://github.com/jankneumann/agentic-coding-tools --skill openspec-sync-specs-jankneumann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually copying and merging delta specifications into the main OpenSpec repository is time‑consuming and error‑prone. This Skill automates the synchronization of change‑specific delta specs with the main specs, ensuring accurate, incremental updates without losing existing content.

Core Features & Use Cases

  • Intelligent Merging: Detects added, modified, removed, and renamed requirements and applies them selectively.
  • User‑Guided Selection: Prompts the user to choose the relevant change when not specified.
  • Spec Creation: Generates new main spec files for capabilities that do not yet exist.
  • Use Case: A product team finalizes a new feature change in openspec/changes/feature‑x/; running this Skill updates all affected main specs automatically.

Quick Start

Run the openspec-sync-specs skill to integrate the change named 'feature-x' into the main specifications.

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 OpenSpec specifications automatically?

To merge delta specs into main OpenSpec specifications, you can automate the synchronization of change-specific delta files, ensuring incremental updates without losing existing content.

What is the best way to synchronize removed and renamed requirements in OpenSpec?

Synchronizing removed and renamed requirements in OpenSpec requires intelligent merging that detects these specific changes and applies them selectively to preserve existing spec content.

How do I apply a specific feature change to main specs from the openspec changes directory?

To apply a specific feature change, run the sync operation which prompts you to choose the relevant change directory if not explicitly specified, updating all affected main specs.

Does OpenSpec spec merging create new main spec files for capabilities that do not exist yet?

Yes, OpenSpec spec merging generates new main spec files automatically for capabilities that do not yet exist in the repository when corresponding delta specs are synchronized.

Can I preserve existing spec content when synchronizing delta spec changes?

You can preserve existing spec content when synchronizing delta spec changes by using intelligent merging that selectively applies added, modified, removed, and renamed requirements.

Why is manually copying delta specifications into the main OpenSpec repository error-prone?

Manually copying delta specifications into the main OpenSpec repository is error-prone because it is time-consuming and lacks automated intelligent merging to accurately track incremental requirement changes.