openspec-sync-specs

You can automatically merge delta spec changes by applying added, modified, removed, and renamed requirements from delta specs directly into main project specs. This intelligent partial merging preserves all existing main spec content not covered by the delta.

The best way to sync requirement changes is to use an automated spec-sync workflow that integrates updated feature scenarios into main specs without rewriting entire files. This eliminates manual merging errors and ensures consistent documentation updates.

Yes, you can generate new main specification files for capabilities lacking existing specs. The process automatically creates new files with placeholder purpose sections and incorporates the added requirements from the delta specs.

Partial spec merging handles removed and renamed requirements by intelligently applying those specific changes from the delta to the main specs. It accurately updates or deletes targeted requirements while preserving the remaining existing content.

No, you do not need to archive a project change before updating main software documentation. You can apply delta specification changes directly to main project specs during the software development workflow without archiving first.