What problem does it solve? Keeping OpenSpec main specifications in sync with change proposals is error-prone when done manually, especially when merges must respect ecommerce domain rules like hiding supplier cost data and keeping domain statuses separate. ## Core Features & Use Cases - Delta Spec Synchronization: Merges delta specs from a named change into the main specs under openspec/specs using the canonical logic in ai-specs/skills/openspec-sync-specs/SKILL.md. - Intelligent Partial Merges: Applies ADDED, MODIFIED, REMOVED, and RENAMED operations while reading docs/base-standards.md and openspec/config.yaml for project context. - Domain Validation: Ensures synced specs never expose supplier cost or internal supplier data and never mix domain statuses. - Use Case: After completing an OpenSpec change proposal for a new product variant feature, run this command to merge its delta specs into the main specs with all ecommerce constraints validated. ## Quick Start Ask the assistant to run the opsx-sync command for a specific change name, for example by saying: sync the delta specs from the add-product-variants change into the main specs.