source-command-opsx-sync

Sync delta specs from an OpenSpec change into main specs.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill source-command-opsx-sync-marcel-carrillo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-command-opsx-sync
Source: https://github.com/Marcel-Carrillo/ProyectosIA/tree/main/.agents/skills/source-command-opsx-sync
Command: npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill source-command-opsx-sync-marcel-carrillo

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about source-command-opsx-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync OpenSpec delta specs into main specs?▼

Invoke the opsx-sync command with the change name as an argument. The skill delegates to the canonical ai-specs/skills/openspec-sync-specs/SKILL.md logic, which merges the change's delta specs into openspec/specs using intelligent partial merges.

What merge operations does OpenSpec spec sync support?▼

The sync supports ADDED, MODIFIED, REMOVED, and RENAMED delta operations. It reads docs/base-standards.md and openspec/config.yaml to apply these merges with project-specific context.

What happens if I run opsx-sync without a change name?▼

The skill infers the change name from context when the argument is missing. If the name is ambiguous or cannot be inferred, it asks the user to clarify before proceeding.

Does spec sync validate ecommerce domain constraints?▼

Yes, the canonical sync logic validates that synced specs never expose supplier cost or internal supplier data and never mix domain statuses. This validation is built into the ai-specs version of the skill.

Should I use the .cursor or .Codex mirrors of openspec-sync-specs?▼

No, the CLI-generated mirrors in .Codex and .cursor are thinner defaults and are not canonical. Always defer to ai-specs/skills/openspec-sync-specs/SKILL.md, which is the single source of truth for the sync logic.