What problem does it solve? Keeping main capability 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 merging, without archiving the change. ## Core Features & Use Cases - Intelligent Requirement Merging: Applies ADDED, MODIFIED, REMOVED, and RENAMED requirement blocks into main specs while preserving existing scenarios and content not mentioned in the delta. - Store-Aware Operation: Supports registered OpenSpec stores via --store <id> flags and resolves the correct specs root from openspec status output. - Safe Capability Retirement: Deletes a spec.md only when strict conditions hold (no remaining requirements, valid Purpose, retire_capabilities: true marker), and validates results with openspec validate --specs. - Use Case: After finishing a change proposal like add-codex-cli-support, ask the agent to sync its delta specs so the main specs reflect the new requirements while the change stays active for implementation. ## Quick Start Ask the agent to sync the delta specs from a named change into the main specs, for example: sync the specs from the add-codex-cli-support change.