openspec-sync-specs

Merge delta specifications into main specs with guardrails for review.

57|17|Updated May 5, 2025
One-click install
npx skills add https://github.com/jerome-benoit/freqai-strategies --skill openspec-sync-specs-jerome-benoit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/jerome-benoit/freqai-strategies/tree/main/.opencode/skills/openspec-sync-specs
Command: npx skills add https://github.com/jerome-benoit/freqai-strategies --skill openspec-sync-specs-jerome-benoit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync delta specs from a change to main specs. This is an agent-driven operation - you will read delta specs and directly edit main specs to apply the changes. This allows intelligent merging (e.g., adding a scenario without copying the entire requirement).

Core Features & Use Cases

  • Agent-driven delta merging: read delta specs and apply changes to main specs with intelligent conflict resolution.
  • Selective updates: prompts for change selection when multiple delta changes exist; merges ADDED/MODIFIED/REMOVED/RENAMED as appropriate.
  • Guardrails and reversibility: preserves existing content not mentioned in delta and produces a summary of updates for review.

Quick Start

Provide delta changes by selecting a change name (if multiple exist), then merge its delta specs into the corresponding main specs using intelligent merging.

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 safely?

To merge delta specs safely, this Skill reads delta files and applies ADDED, MODIFIED, REMOVED, and RENAMED items to main specs using guardrails that preserve existing content. It outputs a consolidated spec state for your review.

What is the best way to synchronize multiple delta specification changes?

Synchronizing multiple delta specification changes is handled by prompting you to select a specific change name when ambiguity exists. The Skill then processes the selected delta updates to merge them efficiently into the corresponding main specs.

Does spec sync preserve existing content when applying delta updates?

Yes, applying delta updates includes built-in guardrails that preserve existing content not mentioned in the delta. The operation produces a summary of updates so you can review what was modified, added, or removed.

Can I selectively apply only specific changes from a delta file?

Yes, you can selectively apply changes because the Skill prompts for change selection when multiple delta changes exist. This agent-driven merging allows intelligent updates like adding a scenario without copying an entire requirement.

What are the limitations of automated delta specification merging?

The primary limitation is handling ambiguity; when multiple changes exist, the process pauses to prompt for change selection rather than auto-merging. It focuses on preserving existing content, meaning you must manually review the consolidated spec state output.

Why use an agent-driven approach for spec synchronization instead of a standard file merge?

Agent-driven spec synchronization allows intelligent merging by directly reading delta specs and editing main specs. This enables contextual updates like adding a single scenario without copying an entire requirement, which standard file merges cannot achieve.