source-command-opsx-sync

Sync delta specs from an OpenSpec change into main specification files.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/jonathanlin768/CS2Match-Nakama --skill source-command-opsx-sync-jonathanlin768
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-command-opsx-sync
Source: https://github.com/jonathanlin768/CS2Match-Nakama/tree/main/.agents/skills/source-command-opsx-sync
Command: npx skills add https://github.com/jonathanlin768/CS2Match-Nakama --skill source-command-opsx-sync-jonathanlin768

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping main specification files in sync with change proposals is tedious and error-prone when done by hand. This Skill applies delta specs (ADDED, MODIFIED, REMOVED, RENAMED requirements) from an OpenSpec change directly into the main specs with intelligent merging. ## Core Features & Use Cases - Delta Spec Application: Reads delta spec files from a change and applies requirement additions, modifications, removals, and renames to main specs under openspec/specs/. - Intelligent Merging: Applies partial updates such as adding a single scenario without copying entire requirements, preserving content not mentioned in the delta. - Interactive Change Selection: Lists available changes via openspec CLI and prompts the user to select one when no change name is provided. - Use Case: After finishing a feature change like add-auth, run the sync to merge its delta requirements into the main capability specs so the canonical documentation reflects the approved design. ## Quick Start Ask the AI to sync the delta specs from a specific change into the main specs, for example by saying: sync the specs from the add-auth change.

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 delta specs from an OpenSpec change to main specs?

Invoke the sync command with a change name, such as /opsx:sync add-auth. The skill reads the delta spec files reported by openspec status and applies each ADDED, MODIFIED, REMOVED, and RENAMED requirement to the corresponding main spec under openspec/specs/.

What happens if I run the sync without specifying a change name?

The skill runs openspec list --json to retrieve available changes and prompts you to select one interactively. It never guesses or auto-selects a change, so ambiguous requests always require explicit user confirmation.

Does syncing a change overwrite existing scenarios in main specs?

No. The merge is intelligent and partial: MODIFIED requirements only apply the scenarios or description changes stated in the delta, and all existing content not mentioned in the delta is preserved. Running the sync twice produces the same result.

Can I sync specs when the change is in workspace-planning mode?

No. If openspec status reports actionContext.mode as workspace-planning, the skill explains that workspace spec sync is not supported and stops. It does not fall back to repo-local paths or edit linked repositories.

What happens when the main spec for a capability does not exist yet?

The skill creates a new spec file at openspec/specs/<capability>/spec.md with a Purpose section (which can be marked TBD) and a Requirements section containing the ADDED requirements from the delta spec.