openspec-sync-specs

Merge delta OpenSpec requirement blocks into main spec files per capability.

1|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/cynkra/cynkra.ai.day --skill openspec-sync-specs-cynkra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/cynkra/cynkra.ai.day/tree/main/indietypst/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/cynkra/cynkra.ai.day --skill openspec-sync-specs-cynkra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of keeping OpenSpec “main” requirements up to date when you create incremental “delta” changes, without losing unrelated existing content.

Core Features & Use Cases

  • Agent-driven intelligent merging: Reads delta spec changes and applies only the specified additions, modifications, removals, or renames to the corresponding main specs.
  • Capability-aware updating: Updates each affected capability’s main spec, or creates a new main spec file when it doesn’t exist yet.
  • Change selection without guessing: If you do not provide a change name, it lists available changes and prompts the user to select, ensuring you apply the correct delta.

Quick Start

Sync the change named "v1-brownfield-adjustments" into the corresponding main specs for all capabilities that have delta 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 sync delta specs into main OpenSpec specs without losing existing content?

Spec synchronization intelligently merges delta OpenSpec requirements into main specs by applying added, modified, removed, and renamed blocks per capability. It preserves unspecified content while updating only the targeted requirement changes.

What does delta merge do when a main spec file doesn't exist yet?

Delta merge automatically creates missing main spec files when a corresponding capability spec doesn't exist yet. This capability-aware updating ensures new specs are generated directly from delta changes without manual file creation.

Do I need the openspec CLI to synchronize requirements?

Yes, spec synchronization requires openspec CLI access to read delta and main spec files and perform intelligent partial merges. The CLI provides the necessary file access for applying requirement changes across capabilities.

How do I apply a specific change to main specs without archiving the change?

Provide the change name to sync a specific delta into main specs without archiving. If no name is provided, the system lists available changes under openspec/changes and prompts you to select the correct delta.

What is the difference between delta specs and main specs in requirements management?

Delta specs contain incremental changes like additions, modifications, removals, and renames, while main specs hold the full current requirements. Syncing merges deltas into main specs to keep requirements up to date without losing unrelated content.

Can agent workflows automate OpenSpec spec synchronization for Claude Code?

Agent-driven intelligent merging automates reading delta spec changes and applying them to corresponding main specs. The workflow handles capability-level updates and outputs a summary of synced requirement blocks per capability.