skills.rest
TE-QuanBZhang
TE-QuanBZhangCOMMUNITY
Explore all skills by this author →
GitHub

opsx-sync

Sync delta specs from an OpenSpec change into main specs via slash command.

1|Updated Jun 27, 2026
Search Tags:#workflow#requirements#slash command#openspec#spec sync#delta specs#codegraph
One-click install
npx skills add https://github.com/TE-QuanBZhang/skills-pool --skill opsx-sync-te-quanbzhang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: opsx-sync
Source: https://github.com/TE-QuanBZhang/skills-pool/tree/main/ai-coding/skills/opsx-sync
Command: npx skills add https://github.com/TE-QuanBZhang/skills-pool --skill opsx-sync-te-quanbzhang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping main specifications in sync with change proposals is tedious and error-prone when done manually. This Skill applies delta specs from an OpenSpec change directly to the main specs, handling added, modified, removed, and renamed requirements intelligently. ## Core Features & Use Cases - Delta Spec Synchronization: Reads delta specs from a change and edits main specs to apply ADDED, MODIFIED, REMOVED, and RENAMED requirements. - Context-Aware Resolution: Uses openspec status --change JSON output and CodeGraph exploration to resolve the right change and capability context before editing. - Use Case: After finishing an implementation change, run /opsx:sync to merge the change's delta specs into the main spec files so the canonical documentation reflects the shipped behavior. ## Quick Start Ask the agent to run /opsx:sync for a specific change name to merge its delta specs into the main specifications.

Frequently Asked Questions about opsx-sync

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

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

Run the /opsx:sync slash command, optionally followed by a change name. The agent resolves the change context with openspec status, finds the delta specs, and edits the main specs to apply the changes.

What does the opsx sync command do with delta specs?▼

It reads delta specs from a change's artifact paths and applies ADDED, MODIFIED, REMOVED, and RENAMED requirement operations directly to the main specification files, then shows a summary of the applied changes.

Does opsx-sync require the openspec CLI?▼

Yes, the skill requires the openspec CLI to resolve change context via openspec status --change with JSON output. It also works alongside CodeGraph for exploring capability terms during the sync.

What happens if I don't specify a change name for /opsx:sync?▼

The skill prompts you to select a change when the target is ambiguous. Providing a change name after the command skips this selection step and resolves the context directly.

When should I run spec sync in the OpenSpec workflow?▼

Run it after a change's implementation is complete and verified, so the delta specs are merged into the main specs. This keeps the canonical specification aligned with the shipped behavior before archiving the change.

Related Skills

Explore More Software Engineering Skills→
BlackBeltTechnologyBlackBeltTechnology

openspec-sync-specs

Merge delta specification changes into main OpenSpec spec files.

Official
Advanced
CoderCoco-StudiosCoderCoco-Studios
1

openspec-archive-change

Archive completed OpenSpec changes after verifying artifacts, tasks, and spec synchronization.

Official
Advanced
agoodwayagoodway

openspec-archive-change

Archive completed openspec workflow changes into dated directories after validating completion.

Official
Advanced
finger-gunfinger-gun
4

openspec-sync-specs

Merge delta specifications into main OpenSpec specs with intelligent changes.

Official
Advanced