skills.rest
brainsnorkel
brainsnorkelCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-sync-specs

Merge delta specifications into main specs for incremental changes.

Updated Feb 1, 2026
Search Tags:#automation#merge#openspec#version-control#delta-specs#spec-management
One-click install
npx skills add https://github.com/brainsnorkel/channel-secrets --skill openspec-sync-specs-brainsnorkel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/brainsnorkel/channel-secrets/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/brainsnorkel/channel-secrets --skill openspec-sync-specs-brainsnorkel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merges delta specifications into the main specs to apply incremental changes without archiving the delta.

Core Features & Use Cases

  • Agent-driven synchronization: read delta specs from openspec/changes and apply to openspec/specs, enabling collaborative spec management.
  • Intelligent merging: supports ADDED, MODIFIED, REMOVED, and RENAMED changes, preserving existing content not mentioned in the delta.
  • Automatic spec creation: creates a new main spec if a capability does not exist yet, with an initial set of added requirements.
  • Guardrails & idempotence: ensures the operation is repeatable and prompts for clarification when needed.

Quick Start

To sync changes, specify the change name and run the spec-sync tool to update the main specs accordingly.

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

Merging delta specs involves reading incremental changes from openspec/changes and applying ADDED, MODIFIED, REMOVED, and RENAMED requirements to openspec/specs while preserving existing unrelated content.

What happens when merging delta specs if the main spec does not exist yet?▼

When merging delta specs, if the target capability does not exist, the operation automatically creates a new main spec and initializes it with the added requirements from the delta file.

Can I apply the same delta spec changes multiple times idempotently?▼

Yes, merging delta specs is designed to be idempotent, meaning applying the same delta file repeatedly yields the same final main spec state without duplicating requirements or corrupting data.

How does spec management handle ambiguous requirements during a merge?▼

During spec management merges, the workflow includes guardrails that detect ambiguous changes and prompt the user for clarification before modifying the main specs.

What is the best way to apply incremental version-control changes to specifications?▼

The best way to apply incremental version-control changes is using an agent-driven synchronization workflow that merges delta specs into main specs to update requirements without archiving the delta.

Related Skills

Explore More Software Engineering Skills→
daodaoedudaodaoedu

openspec-archive-change

Archive completed OpenSpec change directories after validating artifacts and tasks.

Official
Advanced
AdJIaAdJIa

openspec-sync-specs

Merge delta spec changes into main OpenSpec specs idempotently.

Community
Advanced
HsienWHsienW
63

openspec-sync-specs

Synchronize delta specifications into main specifications using the openspec CLI.

Community
Intermediate
rock-hurock-hu

openspec-sync-specs

Merge delta specifications into main OpenSpec repository specs.

Community
Intermediate