openspec-sync-specs

Invoke the skill with a change name, or let it infer the change from context. It reads the delta specs listed in the change status, merges each requirement into the corresponding main spec, then runs openspec validate --specs to confirm the result.

Syncing updates the main specs with the delta content while the change remains active, so documentation stays current during implementation. Archiving is the final step that closes the change after implementation is complete.

No. The merge is intelligent: scenarios and content not mentioned in the delta are preserved in their existing order. A MODIFIED block carries the full requirement, and validation rejects deltas that drop scenarios the main spec still has.

Yes. A caller can narrow the sync to an explicit subset of paths from artifactPaths.specs.existingOutputPaths. The skill syncs only the named paths and never widens the selection back to the full list.

The main spec file is deleted only when strict retirement conditions hold, including a retire_capabilities marker in the change's .openspec.yaml and a well-formed remaining spec. Otherwise the sync stops for that capability and reports the blocking condition.

The sync stops if the openspec instructions command exits non-zero or returns invalid JSON, since artifact rules could not be confirmed. It also stops when no delta specs exist in existingOutputPaths rather than inferring them from other artifacts.