skills.rest
ConductionNL
ConductionNLOFFICIAL
Explore all skills by this author →
WebsiteGitHub

opsx-sync

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

1|Updated Jul 16, 2026
Search Tags:#workflow#markdown#requirements#spec-driven development#openspec#spec sync#delta specs
One-click install
npx skills add https://github.com/ConductionNL/buildiq --skill opsx-sync-conductionnl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: opsx-sync
Source: https://github.com/ConductionNL/buildiq/tree/main/.claude/skills/opsx-sync
Command: npx skills add https://github.com/ConductionNL/buildiq --skill opsx-sync-conductionnl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping main specification files 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 specs with intelligent merging. ## Core Features & Use Cases - Delta Spec Discovery: Locates delta spec files under openspec/changes/<name>/specs/ and parses ADDED, MODIFIED, REMOVED, and RENAMED requirement sections. - Intelligent Merging: Applies partial updates such as adding a single scenario without copying existing ones, preserving content not mentioned in the delta. - New Spec Creation: Creates a new main spec file with Purpose and Requirements sections when a capability does not exist yet. - Use Case: After finishing a change like add-webhook-support, run the sync to merge its three new webhook requirements into openspec/specs/webhooks/spec.md, then archive the change. ## Quick Start Ask the assistant to sync the delta specs from a specific change into the main specs, for example by saying: sync the specs for the add-webhook-support change.

Frequently Asked Questions about opsx-sync

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

Run the sync operation with a change name, such as /opsx-sync add-auth. The skill reads delta specs under openspec/changes/<name>/specs/ and applies ADDED, MODIFIED, REMOVED, and RENAMED requirements to the main specs.

What is a delta spec in OpenSpec?▼

A delta spec is a markdown file under openspec/changes/<name>/specs/<capability>/spec.md describing intended changes. It uses sections like ADDED Requirements, MODIFIED Requirements, REMOVED Requirements, and RENAMED Requirements to express intent rather than full replacements.

Can I add a single scenario without copying existing ones?▼

Yes. Under MODIFIED Requirements, include only the new scenario. The merge is intelligent and partial, preserving existing scenarios and content not mentioned in the delta.

What happens if the main spec does not exist yet?▼

A new main spec is created 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.

Is the spec sync operation idempotent?▼

Yes. Running the sync twice produces the same result, since existing requirements are updated to match the delta rather than duplicated. The change remains active afterward and should be archived once implementation is complete.

Related Skills

Explore More Software Engineering Skills→
UnterrainerInformatikUnterrainerInformatik

openspec-sync-specs

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

Official
Intermediate
nodesourcenodesource
6

openspec-archive-change

Archives completed openspec changes after verifying artifact and task completion status.

Official
Intermediate
CybernetKZCybernetKZ

tz-implement

Implements OpenSpec change proposals through phased stop-gates, logical commits, and spec-delta archival.

Official
Advanced
jeremybrasherjeremybrasher

principle-build-the-lever

Builds rerunnable codemods, scripts, and generators instead of performing edits by hand.

Community
Intermediate