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 to the main specs, merging intelligently instead of overwriting, and without archiving the change. ## Core Features & Use Cases - Intelligent Requirement Merging: Applies ADDED, MODIFIED, REMOVED, and RENAMED requirement blocks from delta specs while preserving untouched content and scenario order in main specs. - Store-Aware Operation: Discovers registered OpenSpec stores via openspec store list --json and scopes all reads and writes with --store <id> when a store is selected. - Safe Guardrails: Verifies the project root before writing, honors caller-narrowed delta subsets, validates results with openspec validate --specs, and handles capability retirement only under strict conditions. - Use Case: After drafting a change with delta specs for a billing capability, ask the agent to sync the specs so the main specs/billing/spec.md gains the new requirements while the change stays active for implementation. ## Quick Start Ask the agent to run openspec sync for a named change, for example: sync the specs from the add-billing-invoices change into the main specs.