openspec-sync-specs

You can sync delta specs to main specs without manual merging by using intelligent partial merging logic. This process applies only added, modified, removed, or renamed requirements from delta specs while preserving unchanged content in the main specification files.

A delta spec represents active project changes containing added, modified, removed, or renamed requirements. It captures the differences that need to be synced to central main specification files without requiring you to rewrite entire unchanged requirement sections.

Yes, new capability spec files are automatically created if they do not already exist in the main openspec directory. This happens during the delta spec synchronization process when a new requirement is applied to the central project specifications.

No, openspec sync does not overwrite unchanged requirement sections. It implements intelligent partial merging logic to update only the changed requirement sections while preserving all unchanged content in the main project specification files.

The best way to apply only modified requirements from a delta spec to main specs is through an automated partial merging workflow. This ensures only the specific added, modified, removed, or renamed requirements are synced without copying entire unchanged sections.