openspec-sync-specs

Merging delta specifications into main specs requires an agent-driven workflow that reads delta changes and intelligently applies them to the primary spec set. This preserves existing unmentioned content and supports partial updates to avoid regressions.

A delta spec sync workflow is an agent-driven process that reads delta specifications and intelligently applies added, modified, or renamed requirements to a main specification set, ensuring safe and traceable updates in development workflows.

Yes, the delta sync process can automatically create a new main spec file if the capability does not exist yet. This ensures your primary specification set is initialized correctly when applying delta changes for the first time.

You can apply partial updates by using intelligent merging during the delta sync process. This mechanism preserves existing main spec content that is not mentioned in the delta, ensuring only added, modified, or renamed requirements are applied.

The best way to manage specification changes is to use a change-management workflow that guides you to review and apply delta merges before archiving and deployment. This ensures safe, traceable updates to your main specification set.

You need to sync delta specs when your development workflow requires careful merging of changes into main specs to avoid regressions. This is necessary whenever requirements are added, modified, or renamed in your delta specifications.