opsx-sync

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

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/moogah/emacs --skill opsx-sync-moogah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opsx-sync
Source: https://github.com/moogah/emacs/tree/main/.claude/skills/opsx-sync
Command: npx skills add https://github.com/moogah/emacs --skill opsx-sync-moogah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables intelligent merging of delta specifications into the canonical main specifications, allowing updates to be propagated without archiving changes.

Core Features & Use Cases

  • Agent-driven merging: read delta specs and apply changes to main specs with intent-based merging.
  • Delta-driven updates: support ADDED, MODIFIED, REMOVED, and RENAMED requirements.
  • Safe synchronization: preserve unrelated content and require user direction for ambiguous changes.

Quick Start

Prompt the agent to sync a delta specification into its corresponding main specs using the provided delta structure.

Frequently Asked Questions about opsx-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I merge delta specs into main OpenSpec specifications?

Merging delta specs into main specifications involves reading changes from openspec/changes/<name>/specs and updating openspec/specs accordingly. The process applies ADDED, MODIFIED, REMOVED, and RENAMED requirements intelligently while preserving existing content.

What does ADDED, MODIFIED, REMOVED, and RENAMED mean when merging delta specs?

These are intent-based change directives applied during delta-driven updates. The merging process reads these directives from delta specs and applies them to canonical main specifications, preserving unrelated content not mentioned in the delta.

Can I sync OpenSpec changes without archiving the delta specifications?

Yes, you can synchronize delta specs into canonical main specifications without archiving changes. This allows updates to be propagated directly into the main OpenSpec specs by applying the delta changes intelligently.

What happens to existing main spec content not mentioned in the delta specs?

Existing main specification content not mentioned in the delta specs is preserved during the merge. The intelligent merging process only applies the specific ADDED, MODIFIED, REMOVED, and RENAMED changes defined in the delta.

How does the merge process handle ambiguous changes in delta specs?

When ambiguous changes are encountered during merging, the process prompts for a change name to clarify the intent. This safe synchronization requires user direction rather than guessing, ensuring accurate updates to main specs.

Is the delta spec merging process idempotent?

Yes, the delta spec merging process is idempotent, meaning applying the same delta changes multiple times produces the same result without unintended duplication or side effects in the main specifications.