openspec-sync-specs

Delta specification merging works by reading changes from openspec/changes and applying them to openspec/specs. It handles ADDED, MODIFIED, REMOVED, and RENAMED requirements with intent-aware logic, preserving existing content not mentioned in the delta.

Idempotent merging means running the operation repeatedly yields the same updated main specs without duplication or rollback. This ensures consistent results when synchronizing delta specifications into the primary OpenSpec definitions.

Yes, OpenSpec sync supports ADDED, MODIFIED, REMOVED, and RENAMED requirement sections. It applies changes with intent-aware merging logic to accurately update main specs based on the delta specification's declared operations.

Running the delta spec merge multiple times is safe because the operation is idempotent. Re-running yields the same updated main specs without duplication or rollback, ensuring consistent synchronization results.

To list available delta changes, run openspec list --json. This displays delta changes under openspec/changes, allowing you to review and select the desired change name before applying it to the main specs.

Yes, OpenSpec sync is designed for codebase maintenance and supports multiple change handling. It reads delta specs from openspec/changes and merges them into openspec/specs, applying each change with intelligent, intent-aware merging.