openspec-sync-specs

Merge OpenSpec delta requirements into main specification files.

Updated Jan 23, 2026

Search Tags:#automation #specifications #merge #OpenSpec #delta #version-control

Ready to run

npx skills add https://github.com/lz-freedom/polybull-stock-helper --skill openspec-sync-specs-lz-freedom

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/lz-freedom/polybull-stock-helper/tree/main/.opencode/skills/openspec-sync-specs
Command: npx skills add https://github.com/lz-freedom/polybull-stock-helper --skill openspec-sync-specs-lz-freedom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the intelligent merging of delta specifications into main OpenSpec specifications, preserving existing content while applying targeted updates from delta specs.

Core Features & Use Cases

Intelligent delta merging: apply ADDED, MODIFIED, REMOVED, and RENAMED requirements to main specs without wholesale replacement.
Delta-driven updates: reads delta specs under openspec/changes/<name>/specs/<capability>/spec.md and updates or creates the corresponding main spec.
Guided execution: when multiple delta changes exist, prompts the user to select the change to apply and then merges changes incrementally.
Audit trail: preserves existing content not mentioned in the delta and documents applied changes for traceability.

Quick Start

List available delta changes with the OpenSpec tool. When prompted, select the change to apply. The tool will read delta specs and update the main specs under openspec/specs, creating new specs if needed and preserving existing content.

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 OpenSpec delta specifications into main specs without losing existing content?▼

To merge OpenSpec delta specifications without losing content, apply ADDED, MODIFIED, REMOVED, and RENAMED requirements to the main specs. This delta-driven operation updates existing blocks and creates new specs while preserving unrelated content.

What are delta specs in OpenSpec and when do I need to apply them?▼

Delta specs in OpenSpec are change files located at openspec/changes/<change>/specs/<capability>/spec.md. You need to apply them when you want to update main specifications with targeted modifications rather than replacing the entire document.

Can I select which delta change to apply when multiple OpenSpec changes exist?▼

Yes, when multiple delta changes exist, the tool prompts you to select the specific change to apply. It then reads the selected delta specs and merges the changes incrementally into the main specifications.

How do I apply ADDED, MODIFIED, REMOVED, and RENAMED requirements to Markdown specs?▼

Applying ADDED, MODIFIED, REMOVED, and RENAMED requirements to Markdown specs involves reading delta files, comparing them against main specs, and writing the targeted updates. This creates new specs if needed and preserves existing unmentioned content.

Does merging delta specs preserve unrelated content in the main OpenSpec specifications?▼

Yes, merging delta specs preserves unrelated content in the main OpenSpec specifications. The intelligent merge operation applies targeted updates from the delta files while maintaining an audit trail of existing content not mentioned in the delta.

What is the best way to automate applying version-controlled specification changes to main specs?▼

The best way to automate applying version-controlled specification changes is using an intelligent delta merging tool that reads OpenSpec delta files, compares them with main specs, and writes updates incrementally while prompting for selection when multiple changes exist.