openspec-sync-specs

Merge delta specifications into canonical OpenSpec files with requirement-level updates.

10|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/joannanowakowska/plannning-poker-app --skill openspec-sync-specs-joannanowakowska
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/joannanowakowska/plannning-poker-app/tree/main/.github/skills/openspec-sync-specs
Command: npx skills add https://github.com/joannanowakowska/plannning-poker-app --skill openspec-sync-specs-joannanowakowska

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you merge delta spec changes into the main OpenSpec documentation without archiving the change, preserving intent while updating the canonical spec.

Core Features & Use Cases

  • Delta-to-main syncing: Reads change-specific spec deltas and applies them to the main spec files.
  • Intelligent merging: Adds, modifies, removes, or renames requirements while preserving unrelated content.
  • Guided change selection: Prompts for a change when none is provided and resolves the correct spec context before editing.
  • Use Case: A product or engineering team has approved spec updates in a change branch and needs the main spec updated in place so implementation can continue.

Quick Start

Use the openspec-sync-specs skill to sync the specified change into the main specs without archiving it.

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 files without losing existing context?

Syncing delta spec changes into canonical OpenSpec files applies requirement-level updates to the main spec set, preserving unrelated content while adding, modifying, removing, or renaming specific requirements.

What is the difference between syncing deltas and wholesale spec replacement?

Delta syncing applies intelligent merging to update only targeted requirements in the main spec files, whereas wholesale replacement overwrites the entire document, losing the context of unrelated approved specifications.

How to apply approved spec updates from a change branch into the main spec set?

Applying approved spec updates uses the OpenSpec CLI to read change-specific deltas and merge them in place into the main spec markdown files, allowing implementation to continue without archiving the change.

Do I need the OpenSpec CLI to sync delta specifications into canonical files?

Yes, syncing delta specifications into canonical OpenSpec files requires OpenSpec CLI access to resolve the correct spec context and perform requirement-aware editing before applying the merged changes.

What happens if I try to sync specs without specifying a change for the delta merge?

Syncing specs without a specified change triggers a guided prompt that asks you to select a change, then resolves the correct spec context before performing any requirement-aware editing on the markdown files.

Can I sync spec changes without archiving the original change branch?

Yes, syncing spec changes merges the delta updates into the main canonical files in place without archiving the original change, preserving the change intent while updating the documentation for ongoing implementation.