openspec-sync-specs

Merge delta specification requirement changes into main specifications.

Updated Jan 9, 2026
One-click install
npx skills add https://github.com/runecalico-ai/second_edition_spellbook --skill openspec-sync-specs-runecalico-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/runecalico-ai/second_edition_spellbook/tree/main/.cursor/skills/openspec-sync-specs
Command: npx skills add https://github.com/runecalico-ai/second_edition_spellbook --skill openspec-sync-specs-runecalico-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec-cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of updating main specifications with changes from delta specifications, allowing for intelligent merging without discarding the work-in-progress.

Core Features & Use Cases

  • Intelligent Merging: Apply additions, modifications, removals, and renames to requirements within specifications.
  • Agent-Driven Operation: Directly edits main specs based on delta specs, facilitating nuanced updates.
  • Use Case: A developer has made changes to a feature's requirements in a delta spec. This Skill can be used to integrate those specific changes (e.g., adding a new scenario to an existing requirement) into the main specification without needing to archive the entire change.

Quick Start

Use the openspec-sync-specs skill to sync changes from the 'feature-enhancement' delta spec to the main specs.

Frequently Asked Questions about openspec-sync-specs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I merge delta specification changes into main requirements without archiving?

To merge delta specification changes without archiving, you can synchronize added, modified, removed, and renamed requirements directly into your main specifications. This approach intelligently integrates feature updates while preserving your work-in-progress.

What is the best way to apply renamed requirements across different capabilities in specs?

Applying renamed requirements across capabilities is handled through intelligent delta merging. This process directly edits main specs based on your delta specs, facilitating nuanced updates for additions, modifications, and removals.

Do I need the openspec CLI to sync delta specifications?

Yes, you need the openspec CLI to sync delta specifications. The CLI is required for listing and managing changes before the agent-driven operation intelligently merges those requirement updates into your main specifications.

Can I add a new scenario to an existing requirement without archiving the entire change?

Yes, you can add a new scenario to an existing requirement without archiving the entire change. By syncing your feature-enhancement delta spec, the Skill integrates specific modifications directly into the main specification.

Why does synchronizing specs preserve work-in-progress instead of finalizing changes?

Synchronizing specs preserves work-in-progress because it updates main specifications with targeted requirement changes rather than fully archiving the delta. This allows continuous intelligent merging of additions, modifications, and renames during development.