skills.rest
lotea-be
lotea-beOFFICIAL
Explore all skills by this author →
GitHub

openspec-sync-specs

Merge delta specs into main OpenSpec specs without archiving.

2|Updated Jun 6, 2026
Search Tags:#automation#workflow#validation#openspec#delta-spec#spec-merge
One-click install
npx skills add https://github.com/lotea-be/qrspi --skill openspec-sync-specs-lotea-be
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/lotea-be/qrspi/tree/main/claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/lotea-be/qrspi --skill openspec-sync-specs-lotea-be

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs often exist separately from main OpenSpec specs. This Skill merges those delta changes into the canonical specs without archiving, ensuring the main specs stay current while preserving change intent.

Core Features & Use Cases

  • Intelligent merging of ADDED, MODIFIED, REMOVED, and RENAMED requirements into main specs.
  • Prompt-driven handling for ambiguous contexts and workspace differences.
  • Guardrails to preserve existing content and avoid unintended deletions.

Quick Start

Provide a delta spec and let the system merge it into the main specs, then review 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 OpenSpec specs without archiving?▼

To merge delta specs into main OpenSpec specs, apply ADDED, MODIFIED, REMOVED, and RENAMED changes directly into repo-local specs. The merge updates or creates openspec/specs/<capability>/spec.md files while preserving existing content and avoiding unintended deletions.

What is a delta spec and when do I need to merge it?▼

A delta spec captures incremental changes separately from canonical OpenSpec specs. You need merging when applying ADDED, MODIFIED, REMOVED, or RENAMED requirements to keep main specs current without archiving, preserving the original change intent.

Do I need the OpenSpec CLI to apply changes to spec.md files?▼

Yes, the OpenSpec CLI is required to merge delta specs into main OpenSpec specs. The process reads delta specs, applies validated changes to openspec/specs/<capability>/spec.md files, and outputs a summary of all modifications made.

How are ambiguous context differences handled during spec merging?▼

Ambiguous contexts and workspace differences during spec merging are handled through prompt-driven user interactions. This guardrail approach ensures safe application of ADDED and MODIFIED requirements while preventing unintended content deletions.

What's the best way to apply REMOVED and RENAMED changes to OpenSpec specs?▼

The best way to apply REMOVED and RENAMED changes is using an intelligent merge process that safely alters repo-local OpenSpec specs. It applies these transformations alongside ADDED and MODIFIED entries, then generates a summary of changes for review.

Related Skills

Explore More Software Engineering Skills→
brandon-setegnbrandon-setegn

openspec-sync-specs

Sync delta specifications into main OpenSpec specs by applying added, modified, removed, and renamed requirements.

Community
Advanced
SiddharthChillaleSiddharthChillale

openspec-sync-specs

Apply ADDED, MODIFIED, REMOVED, and RENAMED delta changes to openspec main spec files.

Community
Advanced
kevinxo328kevinxo328
5

openspec-archive-change

Archive completed openspec workflow changes after validating artifacts and task status.

Community
Advanced
jamie8johnsonjamie8johnson
13

cqs-remove-note

Remove notes from project memory by exact text match using the cqs_remove_note MCP tool.

Community
Basic