openspec-sync-specs

Name: openspec-sync-specs
Availability: InStock
Author: chuangkevin

Merges delta specs into main openspec files via the openspec CLI.

Updated Mar 16, 2026

Search Tags:#automation #requirements #cli #merge #openspec #delta #specs

Ready to run

npx skills add https://github.com/chuangkevin/project-bridge --skill openspec-sync-specs-chuangkevin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/chuangkevin/project-bridge/tree/main/.gemini/skills/openspec-sync-specs
Command: npx skills add https://github.com/chuangkevin/project-bridge --skill openspec-sync-specs-chuangkevin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeping a canonical set of specification files up to date with small, intent-driven change deltas is error-prone when done manually; this Skill automates the careful merging of delta specs into the main openspec specs so changes are applied accurately without overwriting unrelated content.

Core Features & Use Cases

Selective merging: Read delta spec sections (ADDED, MODIFIED, REMOVED, RENAMED) and apply only the intended changes to main spec files.
Idempotent updates: Designed so repeated runs produce the same result and preserve unchanged scenarios and content.
User-confirmed changes: Prompts the user to select which change to apply when ambiguous, suitable for teams managing incremental spec changes via openspec/changes folders.

Quick Start

Run the skill to apply the named change's delta specs into openspec/specs and follow prompts to select the change if not provided.

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

To merge delta specs, run the skill to read change directories under openspec/changes and apply targeted requirement updates to main specs. It selectively merges ADDED, MODIFIED, REMOVED, and RENAMED sections while preserving untouched content.

What is the best way to apply incremental requirement changes to openspec specs?▼

The best way to apply incremental requirement changes is automating the merge of intent-driven delta specs into canonical openspec files. This ensures accurate updates without overwriting unrelated content or risking manual errors.

Does openspec-sync-specs support idempotent updates for spec merging?▼

Yes, openspec-sync-specs supports idempotent updates for spec merging. Repeated runs produce the same result, preserving unchanged scenarios and content while applying only the intended changes from the delta specs.

How do I select a specific change to apply from the openspec/changes folder?▼

To select a specific change, the skill uses the openspec CLI to list and select changes. If a change is not explicitly provided, it prompts you to choose which change to apply from the openspec/changes folder.

Can I use this skill to remove or rename requirements in markdown spec files?▼

Yes, you can use this skill to remove or rename requirements in markdown spec files. It reads delta spec sections including REMOVED and RENAMED, applying those targeted updates to the main specification files.