openspec-sync-specs

Sync delta specifications into main OpenSpec specs by applying added, modified, removed, and renamed requirements.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/brandon-setegn/kafka-test --skill openspec-sync-specs-brandon-setegn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/brandon-setegn/kafka-test/tree/main/.cursor/skills/openspec-sync-specs
Command: npx skills add https://github.com/brandon-setegn/kafka-test --skill openspec-sync-specs-brandon-setegn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you apply a change spec to the main OpenSpec requirements without manually reconstructing or archiving the change, reducing merge errors and saving time.

Core Features & Use Cases

  • Delta-to-main syncing: Reads delta spec files and updates the corresponding main capability specs.
  • Intelligent requirement merging: Adds, modifies, removes, and renames requirements while preserving unaffected content.
  • Use Case: A spec owner has a new change set with added scenarios and a renamed requirement, and uses this Skill to propagate those updates into the main spec cleanly.

Quick Start

Sync the selected OpenSpec change into the main specs and summarize the updated capabilities.

Frequently Asked Questions about openspec-sync-specs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync delta spec changes into main specs without losing existing scenarios?

To sync delta spec changes, this Skill merges added, modified, removed, and renamed requirements into your main OpenSpec specs while preserving unaffected structure. It requires delta spec files, main spec files, and the openspec CLI to execute the update automatically.

What is the best way to apply a change spec to main OpenSpec requirements documentation?

Applying a change spec to OpenSpec requirements is handled by reading the delta files and intelligently merging the changes into main capability documentation. This prevents manual reconstruction errors and saves time during change management workflows.

Do I need the openspec CLI to merge modified and renamed requirements into main specs?

Yes, the openspec CLI is required to merge modified and renamed requirements into main specs. You also need direct access to both the delta spec files and the main specification files for the intelligent merging process to function.

How does delta-to-main syncing handle removed requirements in capability documentation?

Delta-to-main syncing handles removed requirements by applying the deletions specified in the change spec to the main documentation. It updates the capability specs cleanly while ensuring unaffected scenarios and existing structures are preserved.

Can I update multiple renamed requirements in OpenSpec without manually archiving the change?

You can update renamed requirements without manually archiving the change by using this Skill to propagate the updates directly into the main spec. It reads the delta spec and applies the structural changes to the corresponding main capability documentation.