What problem does it solve? Keeping main specifications 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 partial merging instead of wholesale file replacement. ## Core Features & Use Cases - Intelligent Requirement Merging: Applies ADDED, MODIFIED, REMOVED, and RENAMED requirement sections from delta specs while preserving existing scenarios and content not mentioned in the delta. - Store-Aware Operation: Discovers registered OpenSpec stores via openspec store list --json and targets the correct specs root for every read and write. - New Capability Spec Creation: Creates a new main spec with a Purpose section and Requirements section when a capability does not exist yet. - Use Case: After finishing a change that adds a billing scenario to an existing requirement, run the sync to update the main billing spec with just that scenario while leaving the change active for continued work. ## Quick Start Ask the assistant to sync the delta specs from a named change into the main specs, for example: sync the specs from the add-billing change.