openspec-sync-specs

Synchronize delta specs into main OpenSpec specifications with intelligent merging.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/RyanCallahan312/crayon --skill openspec-sync-specs-ryancallahan312
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/RyanCallahan312/crayon/tree/main/.opencode/skills/openspec-sync-specs
Command: npx skills add https://github.com/RyanCallahan312/crayon --skill openspec-sync-specs-ryancallahan312

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs drift from the main specifications; this skill synchronizes delta specs into the primary OpenSpec specs, applying intelligent merges to keep artifacts up to date.

Core Features & Use Cases

  • Intelligent delta merging applies ADDED, MODIFIED, REMOVED, and RENAMED blocks to main specs while preserving unrelated content.
  • Delta discovery reads delta specs from openspec/changes/<change>/specs and updates or creates main specs under openspec/specs.
  • Safe, idempotent operations ensure re-running produces the same result and avoids duplication.
  • Ambiguity handling prompts for clarification when a delta change is unclear.

Quick Start

Run this skill to synchronize all pending delta specs into the main OpenSpec specifications and generate a summary.

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

To merge delta specs into main OpenSpec specifications, run a synchronization process that applies ADDED, MODIFIED, REMOVED, and RENAMED blocks from openspec/changes/ into openspec/specs, preserving existing content. It ensures up-to-date artifacts through intelligent, idempotent merging.

What is delta spec synchronization and when do I need it?

Delta spec synchronization is the process of integrating pending change specifications into primary artifacts to prevent documentation drift. You need it when delta specs in openspec/changes/ accumulate and must be applied to keep main OpenSpec specs current without duplicating content.

How do I apply ADDED, MODIFIED, and REMOVED blocks to existing specifications?

Applying ADDED, MODIFIED, REMOVED, and RENAMED blocks to existing specifications is handled by an intelligent merge process that updates or creates main specs under openspec/specs. It preserves unrelated content and prompts for clarification when delta changes are ambiguous.

Can I re-run spec synchronization without creating duplicate content?

Yes, you can re-run spec synchronization without creating duplicate content because the merging operations are idempotent. Re-running the process on the same delta specs produces identical results, guaranteeing safe updates to main specifications without duplication.

What happens if a delta spec change is ambiguous during the merge?

When a delta spec change is ambiguous during the merge, the synchronization process pauses and prompts for clarification. This ambiguity handling ensures that unclear modifications are resolved before being applied to main OpenSpec specifications.

Does spec synchronization preserve existing content not mentioned in delta specs?

Yes, spec synchronization preserves existing content not mentioned in delta specs. The intelligent merging process only applies targeted ADDED, MODIFIED, REMOVED, and RENAMED blocks, leaving unrelated sections of the main OpenSpec specifications intact.