openspec-sync-specs

Merge delta specs into main specs and summarize updates.

2|2|Updated Sep 20, 2023
One-click install
npx skills add https://github.com/zabiny/klabis --skill openspec-sync-specs-zabiny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/zabiny/klabis/tree/main/.opencode/skills/openspec-sync-specs
Command: npx skills add https://github.com/zabiny/klabis --skill openspec-sync-specs-zabiny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs frequently diverge from main specs, causing confusion and drift. This Skill automates intelligent merging by applying delta changes to main specs, preserving existing content and enabling controlled updates without archiving the change.

Core Features & Use Cases

  • Intelligent merging of ADDED, MODIFIED, REMOVED, and RENAMED requirements from delta specs into the corresponding main specs.
  • Automatic creation of main specs when a capability does not exist yet, with a minimal, purpose-driven initial content.
  • Step-by-step guidance for discovering delta specs, applying changes, and summarizing the updates for auditing.

Quick Start

Invoke the openspec sync-specs workflow to merge delta specs into main specs and verify the updated main 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 merge delta specs into main specs without losing existing content?

The sync-specs workflow handles delta spec merging by intelligently applying ADDED, MODIFIED, REMOVED, and RENAMED requirements to main specs. It preserves existing content and outputs a summary of updates for auditing without archiving the delta.

What happens when merging delta specs and the main spec is missing?

When a main spec is missing during delta spec merging, the workflow automatically creates the main spec file. It initializes the new file with minimal, purpose-driven initial content to establish the missing capability baseline.

How do delta specs handle requirement modifications like renaming or removing?

Delta specs handle requirement modifications through intelligent merging logic that explicitly processes ADDED, MODIFIED, REMOVED, and RENAMED requirements. This ensures controlled updates are applied directly to the main specs without archiving.

Is there a way to automate spec merging to prevent drift between delta and main specs?

Automated spec merging prevents drift by applying delta spec changes directly into main specs. This workflow discovers delta specs, intelligently merges the requirement changes, and outputs an update summary for auditing.

Do I need to archive delta specs after merging changes into main specs?

You do not need to archive delta specs after merging. The workflow enables controlled updates by applying delta changes directly to main specs, bypassing the archiving step while preserving existing content.