Is the sync process safe to run multiple times?

Yes, the operation is idempotent. Running the sync twice on the same delta will result in the same state, preventing duplicate requirements or redundant updates.

Does this skill overwrite my existing main specifications?

No, it performs an intelligent merge. It only applies the specific changes described in the delta spec, such as adding a new scenario or updating a description, while keeping unmentioned content intact.

How do I choose which change to synchronize?

If you don't provide a change name, the skill will list all available changes with delta specs and prompt you to select the correct one via the AskUserQuestion tool.

What happens if a main spec file doesn't exist yet?

The skill will automatically create a new main specification file for that capability, set up a basic structure, and populate it with the added requirements from your delta.

OpenSpec Sync

Name: OpenSpec Sync
Author: durandom

bydurandom

Content Management

Synchronizes incremental specification changes from delta files to main project documentation using intelligent merging.

About

The OpenSpec Sync skill automates the process of maintaining project requirements by merging delta specifications from specific change folders into the main specification repository. Instead of a simple overwrite, it acts as an intelligent agent that parses ADDED, MODIFIED, REMOVED, or RENAMED blocks to update your main specs while preserving existing context and scenarios. This ensures your documentation stays in lockstep with feature development without requiring manual copy-pasting or complex version control maneuvers for individual requirements.

Key Features

Intelligent merging that preserves existing scenarios and descriptions
Support for ADDED, MODIFIED, REMOVED, and RENAMED requirement types
Interactive selection of active changes using JSON-based discovery
Automatic generation of new main spec files for new capabilities
0 GitHub stars
Idempotent operations to ensure consistent results across multiple runs

Use Cases

Updating project requirements after a design iteration for a new feature
Refactoring requirement names and structures across a complex system
Merging experimental feature specs into the core project documentation

About

Key Features

Intelligent merging that preserves existing scenarios and descriptions
Support for ADDED, MODIFIED, REMOVED, and RENAMED requirement types
Interactive selection of active changes using JSON-based discovery
Automatic generation of new main spec files for new capabilities
0 GitHub stars
Idempotent operations to ensure consistent results across multiple runs

Use Cases

Updating project requirements after a design iteration for a new feature
Refactoring requirement names and structures across a complex system
Merging experimental feature specs into the core project documentation