openspec-sync-specs

Merge delta specifications into main specifications with intelligent merging rules.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs propose incremental changes; this skill merges those deltas into the main specifications, ensuring the canonical spec stays up-to-date without archiving changes.

Core Features & Use Cases

  • Agent-driven delta merging: reads delta specifications and applies changes to main specs with intelligent merging, preserving untouched content.
  • Comprehensive change handling: supports ADDED, MODIFIED, REMOVED, and RENAMED requirements, merging changes without wholesale replacement.
  • Safety and idempotence: validates existence, creates missing main specs when needed, and remains idempotent on repeated runs.

Quick Start

Provide a delta change name to start syncing delta specs into the main specs with the openspec CLI.

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

To merge delta specs into main specifications, provide a delta change name to sync changes from openspec/changes into the main specs using the openspec CLI. The tool applies intelligent merging rules to apply the changes.

What happens to untouched requirements when syncing delta changes?

When syncing delta changes, unrelated content and untouched requirements are preserved without wholesale replacement. The merge process only applies added, modified, removed, and renamed requirements to the main specification files.

Does openspec create missing main spec files during a merge?

Yes, merging delta changes creates missing main spec files when needed and records a summary of updates. It validates existence before applying changes to ensure the canonical spec stays up-to-date.

Is the delta spec merging process idempotent on repeated runs?

Yes, merging delta specs into main specifications is idempotent on repeated runs. Running the sync process multiple times for the same delta change will not duplicate or corrupt the main specification entries.

How do I handle ambiguous change names when merging openspec deltas?

When merging openspec deltas with ambiguous change names, the process prompts you to specify the exact change name. Providing the correct name ensures the right delta specifications are applied to the main specs.

What types of requirement changes can I apply to main specs?

You can apply ADDED, MODIFIED, REMOVED, and RENAMED requirement changes to main specs. The merge process handles all these delta spec change types intelligently without replacing the entire specification file.