openspec-sync-specs

Merge delta specification changes into main openspec spec files.

1|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/psacc/omnisess --skill openspec-sync-specs-psacc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/psacc/omnisess/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/psacc/omnisess --skill openspec-sync-specs-psacc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps main openspec specification files up to date by applying changes from delta specs without wholesale replacement or accidental loss of existing content, reducing manual editing and merge errors.

Core Features & Use Cases

  • Prompt the user to select a named change and locate delta spec files under openspec/changes/<name>/specs/*/spec.md.
  • Parse ADDED, MODIFIED, REMOVED, and RENAMED sections and apply intelligent, idempotent merges into openspec/specs/<capability>/spec.md, creating new spec files when needed.
  • Preserve unrelated scenarios and content, summarize applied updates, and require user choice when change selection is ambiguous; ideal for maintainers updating main specs from iterative change sets.

Quick Start

Use the skill to apply the change named my-change and merge its delta specs into the main openspec specs.

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 openspec specification files?

To merge delta spec changes into main openspec specification files, use this skill to apply ADDED, MODIFIED, REMOVED, and RENAMED sections from delta specs into the target spec.md files intelligently.

What is the best way to apply changes from an openspec delta spec without losing existing content?

Applying changes from an openspec delta spec without losing existing content requires an idempotent merge process that preserves unrelated scenarios while applying targeted requirement updates to the main specification.

How do I sync openspec change directories to update main spec files?

Sync openspec change directories by selecting a named change, parsing its delta spec files under openspec/changes/<name>/specs/*/spec.md, and merging the requirements into openspec/specs/<capability>/spec.md.

Does openspec spec sync create new specification files when needed?

Yes, openspec spec sync creates new spec files when a delta spec targets a capability that does not yet have an existing openspec/specs/<capability>/spec.md file in the repository.

What happens when a delta spec merge encounters ambiguous changes?

When a delta spec merge encounters ambiguous changes, the process pauses and prompts the user to make a choice, ensuring that unclear modifications are resolved manually before committing to the main spec.

Can I re-run spec syncing multiple times without duplicating requirements?

Yes, you can re-run spec syncing multiple times without duplicating requirements because the merge process is idempotent, meaning applying the same delta spec changes repeatedly yields the same final specification output.