openspec-sync-specs

Sync delta specs from an OpenSpec change into main specification files.

Updated Apr 20, 2020
One-click install
npx skills add https://github.com/UnterrainerInformatik/java-rdb-utils --skill openspec-sync-specs-unterrainerinformatik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/UnterrainerInformatik/java-rdb-utils/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/UnterrainerInformatik/java-rdb-utils --skill openspec-sync-specs-unterrainerinformatik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping main specifications in sync with change proposals is tedious and error-prone when done by hand. This Skill applies delta specs (ADDED, MODIFIED, REMOVED, RENAMED requirements) from an OpenSpec change directly to the main spec files, without archiving the change. ## Core Features & Use Cases - Intelligent Merging: Applies partial updates such as adding a single scenario to an existing requirement without copying unchanged content. - Full Delta Support: Handles ADDED, MODIFIED, REMOVED, and RENAMED requirement sections in delta spec files. - New Capability Creation: Creates a new main spec file with Purpose and Requirements sections when a capability does not exist yet. - Use Case: After drafting a change proposal in openspec/changes/, ask the agent to sync its delta specs so the main specs under openspec/specs/ reflect the new requirements while the change stays active. ## Quick Start Ask the agent to sync the delta specs from a specific OpenSpec change into the main specs, or let it list available changes so you can pick one.

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 OpenSpec delta specs to main specs?▼

Provide a change name, or let the agent run openspec list --json and prompt you to select a change. It then reads each delta spec under openspec/changes/<name>/specs and applies the ADDED, MODIFIED, REMOVED, and RENAMED sections to the matching main spec.

What is the delta spec format in OpenSpec?▼

Delta specs use markdown sections: ADDED Requirements for new requirements, MODIFIED Requirements for changes to existing ones, REMOVED Requirements for deletions, and RENAMED Requirements using FROM:/TO: lines. Scenarios use WHEN/THEN bullet format.

Does syncing specs archive the OpenSpec change?▼

No, syncing only updates the main specs and leaves the change active. You archive the change separately once the implementation is complete.

What happens if the main spec for a capability does not exist?▼

The skill creates a new main spec file at openspec/specs/<capability>/spec.md with a brief Purpose section (marked TBD) and a Requirements section containing the ADDED requirements from the delta.

Is the OpenSpec sync operation idempotent?▼

Yes, the operation is designed to be idempotent, so running it twice produces the same result. Existing requirements matching an ADDED entry are updated in place rather than duplicated.