openspec-sync-specs

Name: openspec-sync-specs
Availability: InStock
Author: Artagon

Merge delta OpenSpec requirement changes into main capability specs.

Updated Nov 12, 2025

Search Tags:#requirements management #openspec #spec synchronization #delta specs #idempotent updates #intelligent merging

Ready to run

npx skills add https://github.com/artagon/artagon-vscode-profiles --skill openspec-sync-specs-artagon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/artagon/artagon-vscode-profiles/tree/main/agents/skills/openspec-sync-specs
Command: npx skills add https://github.com/artagon/artagon-vscode-profiles --skill openspec-sync-specs-artagon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It synchronizes changes captured in a delta spec back into the corresponding main specs, so the authoritative requirements stay current without archiving the change.

Core Features & Use Cases

Agent-driven intelligent merging: Applies ADDED, MODIFIED, REMOVED, and RENAMED requirement updates while preserving any main-spec content not mentioned in the delta.
Interactive change selection: If the change name is omitted, it lists available deltas with delta specs and requires the user to select one (no guessing).
Automatic creation of missing capabilities: When a capability main spec does not exist yet, it creates the spec file and seeds it with Purpose and Requirements from the delta.

Quick Start

Run the openspec-sync-specs operation and, if needed, select the change name from the list produced by openspec so it can 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 OpenSpec delta changes into main requirements specifications?▼

Yes, when a capability main spec does not exist, the synchronization process automatically creates the missing spec file and seeds it with Purpose and Requirements extracted directly from the delta.

How does spec synchronization handle requirements that are not mentioned in the delta?▼

Spec synchronization preserves any main-spec content not mentioned in the delta, ensuring that only the specified added, modified, removed, or renamed requirements are updated during the intelligent merging process.

What happens if I run spec synchronization without specifying a change name?▼

If the change name is omitted, the operation lists available deltas using openspec list and requires the user to interactively select one, preventing the system from guessing the intended change.

Does OpenSpec spec synchronization support idempotent updates for main specs?▼

Yes, OpenSpec spec synchronization supports idempotent updates, producing a consistent summary of updated capabilities and ensuring applying the same delta multiple times yields the same final main spec state.

Can I create a new capability main spec automatically from a delta?▼

Yes, when a capability main spec does not exist, the synchronization process automatically creates the missing spec file and seeds it with Purpose and Requirements extracted directly from the delta.