openspec-sync-specs

Merge delta specifications into main specs across ADDED, MODIFIED, REMOVED, and RENAMED changes.

9|4|Updated Jun 13, 2023
One-click install
npx skills add https://github.com/lbrlabs/pulumi-lbrlabs-eks --skill openspec-sync-specs-lbrlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/lbrlabs/pulumi-lbrlabs-eks/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/lbrlabs/pulumi-lbrlabs-eks --skill openspec-sync-specs-lbrlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

Core Features & Use Cases

  • Reads delta specs located under openspec/changes/<change>/specs
  • Applies changes to main specs across ADDED, MODIFIED, REMOVED, and RENAMED sections
  • Creates new main specs if they do not exist and produces a summary of updates

Quick Start

Run the openspec sync workflow to merge delta specs into the corresponding main specs for a chosen change.

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 archiving the change?

To merge delta specs into main specs, apply ADDED, MODIFIED, REMOVED, and RENAMED changes from openspec/changes to openspec/specs. This updates main specifications while preserving existing content and avoiding unintended deletions.

What happens if a main spec does not exist when syncing delta specs?

When a main spec does not exist during delta spec synchronization, the process automatically creates a new main spec file. It applies the delta changes directly to the new specification and outputs a human-readable summary of the updates.

How does the delta spec merge process handle modified and renamed requirements?

The delta spec merge process intelligently applies MODIFIED and RENAMED changes by validating inputs to avoid unintended deletions. It preserves existing content in main specs while updating the specified requirements across openspec directories.

Can I update main specifications with only ADDED sections from a delta spec?

Yes, you can update main specs with only ADDED sections from a delta spec. The merge process supports applying individual change types like ADDED, MODIFIED, REMOVED, or RENAMED independently while preserving the original main spec content.

What is the best way to synchronize openspec changes without losing existing spec content?

The best way to synchronize openspec changes without losing content is to use an automated delta spec merge. It reads delta and main specs, intelligently applies changes, and validates inputs to prevent unintended data loss during the update.

Why does my delta spec sync output a summary of updates?

A delta spec sync outputs a human-readable summary of updates to provide visibility into how ADDED, MODIFIED, REMOVED, and RENAMED changes were applied to the main specs. This helps track exactly what content was altered or created.