openspec-sync-specs

Sync delta specifications to main specifications in OpenSpec repositories.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MattJColes/macols-configs --skill openspec-sync-specs-mattjcoles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/MattJColes/macols-configs/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/MattJColes/macols-configs --skill openspec-sync-specs-mattjcoles

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of updating main specifications with changes from delta specs without archiving the changes, streamlining the process for spec-driven development.

Core Features & Use Cases

  • Delta Spec Sync: Automatically synchronize changes from delta specs to main specs.
  • Agent-Driven Operation: Allows for intelligent merging of changes, avoiding the need to manually copy entire requirements.
  • Store Selection: Supports selection of a specific store for the operation, enabling focused updates.
  • Quick Start: Use this Skill to update main specs with changes from a specified delta spec in a registered store.

Quick Start

Run the command: skill openspec-sync-specs --store <store_id> --change <change_name>

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 specs to main specs in OpenSpec?

To sync delta specs to main specs in OpenSpec, run the skill with your store ID and change name. This intelligently merges changes without archiving the delta spec.

Do I need the OpenSpec CLI to synchronize specifications?

Yes, you need the OpenSpec CLI installed. This skill requires the CLI to manage spec-driven development and apply selective updates to your repositories.

What is the best way to update main specifications without archiving changes?

The best way to update main specifications without archiving changes is using an intelligent delta spec sync. This agent-driven operation merges specific requirements selectively.

Can I target a specific store when merging delta specifications?

Yes, you can target a specific store during the merge. The command supports store selection via the `--store` parameter for focused specification updates.

Why use agent-driven merging instead of copying entire requirements for spec updates?

Agent-driven merging avoids manually copying entire requirements. It intelligently applies selective updates from delta specs to main specs for efficient synchronization.

What command starts the specification synchronization process?

Run `skill openspec-sync-specs --store <store_id> --change <change_name>` to start synchronizing your delta specifications to the main specifications.