openspec-sync-specs

Merge incremental OpenSpec delta requirements into main capability spec files.

Updated May 5, 2026
One-click install
npx skills add https://github.com/agoodway/goodday --skill openspec-sync-specs-agoodway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/agoodway/goodday/tree/main/.opencode/skills/openspec-sync-specs
Command: npx skills add https://github.com/agoodway/goodday --skill openspec-sync-specs-agoodway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps OpenSpec documentation accurate by applying incremental changes from a delta spec into the corresponding main specs, without deleting or overwriting unrelated content.

Core Features & Use Cases

  • Sync delta → main: Applies ADDED, MODIFIED, REMOVED, and RENAMED requirement changes from openspec/changes/<change>/specs/ into openspec/specs/.
  • Intelligent merging: Preserves main spec scenarios and sections not referenced by the delta, adding only what’s intended.
  • Capability-level updates: Updates existing capability specs or creates new main spec files when a capability doesn’t yet exist.
  • Interactive change selection: Prompts the user to choose when a change name is not provided and inference is ambiguous.
  • Idempotent guardrails: Reads both delta and main specs before editing, and aims to make repeated runs yield the same end state.

Quick Start

Tell the AI which change you want to sync (or ask it to prompt you if you are unsure), and it will update the main spec files by merging the delta requirements into the correct capabilities.

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

Merging OpenSpec delta specs requires applying added, modified, removed, and renamed requirements from openspec/changes/ into openspec/specs/. The process updates or creates main spec files per capability while preserving non-mentioned content.

Does spec synchronization overwrite existing scenarios in main specs?

Spec synchronization does not overwrite existing scenarios; it performs intelligent partial merges that preserve main spec sections not referenced by the delta, adding only the intended changes without deleting unrelated content.

What happens when a capability doesn't exist in main specs during a sync?

When a capability doesn't exist in main specs, the sync process creates a new main spec file for that capability under openspec/specs/. It updates existing specs or creates new files per capability as needed.

How do I select which change to sync when multiple OpenSpec changes exist?

When a change name is not provided and inference is ambiguous, the process interactively prompts you to choose the correct change. It uses the openspec CLI for change discovery when needed to list available options.

Can I run spec synchronization multiple times without duplicating requirements?

Yes, spec synchronization includes idempotent guardrails that read both delta and main specs before editing, aiming to make repeated runs yield the same end state without duplicating applied requirements.

Do I need the openspec CLI to sync delta specifications?

You need the openspec CLI for change discovery when needed, especially to identify and select changes before merging delta requirements into the corresponding main spec files.