Merge delta spec changes into main specification sets.
npx skills add https://github.com/hmj1026/docker_run --skill openspec-sync-specs-hmj1026
Please help me install this Agent Skill. Skill: openspec-sync-specs Source: https://github.com/hmj1026/docker_run/tree/main/.gemini/skills/openspec-sync-specs Command: npx skills add https://github.com/hmj1026/docker_run --skill openspec-sync-specs-hmj1026
Delta specs can diverge from main specs; this skill provides an agent-driven workflow to merge delta changes back into main specs.
Use openspec-sync-specs to synchronize delta changes into the main specs.
High-intent search queries and answers about installing and using this skill.
Merging delta specs involves applying adds, mods, and removes from the delta specification into the main specs. This process intelligently applies changes while preserving existing content.
Synchronizing delta specs uses an agent-driven workflow that reads both delta and main specification files, prompts the user for change selection when ambiguous, and generates a Specs Synced summary for review.
When multiple delta specs exist during synchronization, the workflow provides interactive delta discovery. It prompts you to select the specific change you want to apply to the main specification set.
Yes, you can review changes before archiving synced specifications. The workflow outputs an audit-ready Specs Synced summary that concisely documents all applied changes for your review.
You need delta specs when your working changes diverge from main specs and must be merged back. They provide a structured format to define ADDED, MODIFIED, and REMOVED changes for synchronization.
wonderslifeMerge delta specs into main specs with ADDED, MODIFIED, REMOVED, and RENAMED changes.
jacobcyArchive completed OpenSpec changes with artifact status checks and spec synchronization.
harqianArchive completed changes in the experimental workflow with openspec CLI.
peancharoenCompares specification versions and reports semantic differences with risk assessments.
