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 without archiving the change, using intelligent partial merging instead of wholesale file replacement. ## Core Features & Use Cases - Intelligent requirement merging: Adds new requirements, applies partial modifications (e.g., adding a single scenario without copying existing ones), removes deprecated requirements, and handles renames. - Store-aware operation: Discovers registered OpenSpec stores via openspec store list --json and targets the correct specs root for every read and write. - Guardrailed workflow: Uses only artifactPaths.specs.existingOutputPaths as the delta source, honors caller-narrowed subsets, fetches artifact rules once, and stops before any write on invalid instruction responses. - Use Case: After drafting a change with delta specs for a billing capability, ask the agent to sync those deltas into the main specs so the canonical documentation reflects the new requirements while the change stays active. ## Quick Start Ask the agent to sync the delta specs from a named OpenSpec change into the main specs, for example by saying "sync the specs from the add-billing change".
