opsx-sync

Merge delta specs into main specs with idempotent updates.

9|2|Updated Mar 12, 2026

Search Tags:#automation #requirements #openspec #change-management #delta-specs #main-specs #spec-merging

Ready to run

npx skills add https://github.com/fjpulidop/specrails-core --skill opsx-sync

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: opsx-sync
Source: https://github.com/fjpulidop/specrails-core/tree/main/specrails-plugin/skills/opsx-sync
Command: npx skills add https://github.com/fjpulidop/specrails-core --skill opsx-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merges delta specs into main specs by intelligently applying changes from delta specifications to the primary specification set, ensuring traceability and safety.

Core Features & Use Cases

Intelligent delta merging: read delta specs and apply changes to main specs with context-aware rules.
Safe content preservation: preserves content not mentioned in the delta and resolves ambiguities with prompts when needed.
End-to-end updates: produces a summary of updates and keeps the delta active for audit.

Quick Start

Run a delta-based merge to update main specs from a delta spec and review the resulting changes.

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 specs without losing existing content?▼

Delta specs capture incremental changes like ADDED, MODIFIED, REMOVED, and RENAMED requirements across capabilities. Merging them integrates these specific changes into your main specs while preserving existing content and maintaining traceability.

How does spec merging handle ambiguous changes in delta specifications?▼

Spec merging handles ambiguous changes by prompting the user for clarification before applying updates. This ensures safe content preservation and prevents unintended modifications to the primary specification set.

Can I apply ADDED, MODIFIED, REMOVED, and RENAMED requirements across capabilities in one pass?▼

Yes, you can apply ADDED, MODIFIED, REMOVED, and RENAMED requirements across capabilities in a single merge pass. The process uses context-aware rules to update main specs and generates a concise summary of changes.

What is the best way to keep delta specs active for audit after merging into main specs?▼

The best way to keep delta specs active for audit is to use a delta-driven workflow that merges changes into main specs while retaining the delta. This produces an update summary and maintains the delta for audit traceability.

Do I need OpenSpec workflows to use delta-driven change management for requirements?▼

Delta-driven change management is applicable to OpenSpec workflows. You define targeted requirement changes in delta specs, then merge them into the primary specification set to ensure traceability and safe content preservation.