skills.rest
beliciobcardoso
beliciobcardosoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-sync-specs

Sync delta specs from OpenSpec changes into main specification files.

Updated Mar 17, 2026
Search Tags:#documentation#requirements#merge#spec-driven development#openspec#spec sync#delta specs
One-click install
npx skills add https://github.com/beliciobcardoso/mcp-postgres --skill openspec-sync-specs-beliciobcardoso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/beliciobcardoso/mcp-postgres/tree/main/.qwen/skills/openspec-sync-specs
Command: npx skills add https://github.com/beliciobcardoso/mcp-postgres --skill openspec-sync-specs-beliciobcardoso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping main specifications aligned with change proposals is tedious and error-prone when done manually. This Skill applies delta specs (ADDED, MODIFIED, REMOVED, RENAMED requirements) from an OpenSpec change directly into 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. - Delta Spec Parsing: Reads delta spec files under openspec/changes/<name>/specs/ and interprets ADDED, MODIFIED, REMOVED, and RENAMED requirement sections. - New Spec Creation: Creates new main spec files with Purpose and Requirements sections when a capability does not yet exist. - Use Case: After drafting a change proposal with delta specs, ask the agent to sync them so the main specs reflect the new requirements while the change stays active for implementation. ## 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 delta specs to main specs in OpenSpec?▼

Invoke the sync operation with a change name, or let the agent run openspec list --json and prompt you to select a change. It reads each delta spec under openspec/changes/<name>/specs/ and applies the changes to the corresponding main spec files.

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: pairs. Each requirement can contain scenarios with WHEN/THEN clauses.

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 implementation is complete, keeping the proposal available for continued work.

What happens if a capability has no main spec yet?▼

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

Is the OpenSpec spec sync operation idempotent?▼

Yes, the operation is designed to be idempotent, so running it twice produces the same result. Existing requirements are updated in place rather than duplicated, and content not mentioned in the delta is preserved.

Related Skills

Explore More Software Engineering Skills→
CatsofsufferingCatsofsuffering
5

openspec-sync-specs

Merge delta specs into main OpenSpec specification files.

Community
Advanced
captaincontratcaptaincontrat

openspec-archive-change

Archives completed OpenSpec changes with metadata preservation using the openspec CLI.

Official
Advanced
ConductionNLConductionNL
1

opsx-sync

Sync delta specs from an OpenSpec change into main capability specs.

Official
Intermediate
zgsm-aizgsm-ai
4.4k

roo-conflict-resolution

Resolve Git merge conflicts using commit history and code intent.

Official
Advanced