openspec-sync-specs

Merge delta specification requirement changes into main specifications using the openspec CLI.

1|Updated Feb 13, 2026

Search Tags:#requirements #gitops #sync #openspec #delta #specs

Ready to run

npx skills add https://github.com/em-jones/staccato-toolkit --skill openspec-sync-specs-em-jones

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/em-jones/staccato-toolkit/tree/main/.opencode/skills/openspec-sync-specs
Command: npx skills add https://github.com/em-jones/staccato-toolkit --skill openspec-sync-specs-em-jones

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of updating main specifications with changes from delta specifications, allowing for intelligent merging of requirements without needing to archive the source change.

Core Features & Use Cases

Intelligent Merging: Applies additions, modifications, removals, and renames of requirements to main specs.
Contextual Change Selection: Infers or prompts for the specific change to sync based on conversation context.
Use Case: When a developer has made incremental updates to requirements in a delta spec and wants to integrate those specific changes into the main specification before the entire feature is complete.

Quick Start

Use the openspec-sync-specs skill to sync the changes from the 'new-login-flow' change.

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 specifications into main specs without archiving?▼

To merge delta specifications into main specs without archiving, this Skill intelligently applies additions, modifications, removals, and renames of requirements while preserving existing content. It infers or prompts for the specific change to sync based on conversation context.

How does requirement synchronization handle modifications and renames in specs?▼

Requirement synchronization handles modifications and renames by intelligently merging these changes into the main specifications. It updates the target capabilities directly, preserving existing content while applying the specific requirement changes from the delta spec.

Do I need the openspec CLI to sync requirement changes?▼

Yes, you need the openspec CLI to sync requirement changes. The Skill requires the CLI for listing available delta specifications and applying the selected changes to the main specifications.

When should I sync delta specs into main specifications?▼

You should sync delta specs into main specifications when you have made incremental updates to requirements and want to integrate those specific changes before the entire feature is complete. This avoids the need to archive the source change prematurely.

Can I select which specific delta changes to sync into main specs?▼

Yes, you can select specific delta changes to sync. The Skill supports contextual change selection, automatically inferring the target change from your conversation context or prompting you to specify which delta specification to apply.

Does syncing requirements with this approach preserve existing content in main specs?▼

Syncing requirements with this approach preserves existing content in main specs. The intelligent merge process applies additions, modifications, removals, and renames across capabilities while retaining the unaffected portions of your main specifications.