openspec-sync-specs

To merge delta specs into main specs without overwriting existing content, apply an incremental merge strategy that parses ADDED, MODIFIED, REMOVED, and RENAMED sections to update only intended requirements while preserving unrelated baseline scenarios.

Delta spec synchronization integrates incremental requirement changes from multiple collaborators into a baseline main spec. It applies non-destructive updates by parsing delta structures and applying section-specific changes, ensuring the main spec reflects all workstream modifications without losing existing content.

To apply ADDED, MODIFIED, REMOVED, and RENAMED sections when syncing specifications, parse the delta spec structure and execute the corresponding update logic on the main spec, appending new content, updating existing scenarios, and removing or renaming outdated requirements accordingly.

Yes, you can use incremental spec merging for multi-change collaborative workflows. It supports delta-driven collaboration by sequentially applying multiple delta changes to main specs while maintaining a changelog of applied deltas to track all modifications.

To start syncing specs with a single delta change name, provide that specific delta change identifier to the merge process. The system will locate the corresponding delta spec and intelligently integrate its changes into the main specifications.

The limitation of non-destructive delta spec merging is that it strictly preserves existing baseline requirements and unrelated content. It only applies explicitly defined ADDED, MODIFIED, REMOVED, or RENAMED sections, meaning undefined structural changes or conflicting modifications may not be automatically resolved.