openspec-sync-specs

Merge delta spec changes into main OpenSpec specification files.

Updated Dec 25, 2025
One-click install
npx skills add https://github.com/wtg42/tty-clock-timer --skill openspec-sync-specs-wtg42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/wtg42/tty-clock-timer/tree/main/.opencode/skills/openspec-sync-specs
Command: npx skills add https://github.com/wtg42/tty-clock-timer --skill openspec-sync-specs-wtg42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps main specification files up to date by applying focused changes from delta specs so maintainers do not have to manually copy, merge, or reconstruct updates across capabilities.

Core Features & Use Cases

  • Agent-driven selection of a change set and discovery of delta spec files under openspec/changes/<name>/specs/*/spec.md.
  • Intelligent merging of ADDED, MODIFIED, REMOVED, and RENAMED requirement sections into corresponding openspec/specs/<capability>/spec.md while preserving unrelated content.
  • Creates missing capability spec files, prompts the user to resolve ambiguous change names, and summarizes applied updates for review and auditing.

Quick Start

Sync the change named CHANGE_NAME from openspec/changes into the main specs and return a concise summary of what was added, modified, removed, or renamed.

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 spec changes into main spec files?

To merge delta spec changes, sync specification modifications from openspec/changes into openspec/specs. The process detects ADDED, MODIFIED, REMOVED, and RENAMED directives to update main spec files while preserving unrelated content.

What is a delta spec and when do I need to sync it?

A delta spec contains focused requirement changes for a specific capability. You need to sync a delta spec when you want to apply these changes to main specification files without manually copying or reconstructing updates across capabilities.

How do I apply ADDED, MODIFIED, and REMOVED requirement directives to capability specs?

Applying requirement directives involves reading change files from openspec/changes and intelligently merging them into openspec/specs. It automatically creates missing capability spec files and produces a summarized report of all applied updates.

Does openspec-sync-specs work with ambiguous change names?

Yes, when ambiguous change names are detected during the merge process, it prompts the user to manually select the correct change set. This ensures the proper delta specification files are synced into the main specs.

Can I update main specs without losing existing requirement content?

Yes, merging delta specs preserves unchanged content within main specification files. It only applies the targeted ADDED, MODIFIED, REMOVED, or RENAMED requirement directives while keeping all unrelated sections intact.