openspec-sync-specs

Merge delta specifications into main specifications under openspec directories.

Updated Jan 13, 2026
One-click install
npx skills add https://github.com/MaplumeX/Blockwise --skill openspec-sync-specs-maplumex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/MaplumeX/Blockwise/tree/main/.opencode/skills/openspec-sync-specs
Command: npx skills add https://github.com/MaplumeX/Blockwise --skill openspec-sync-specs-maplumex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs often drift from the main specifications. This Skill provides a safe, repeatable process to merge changes from delta specs into the primary specs, ensuring updates are applied without archiving or losing work.

Core Features & Use Cases

  • Intelligent delta merging: identify added, modified, removed, and renamed requirements and apply them to the main specs with minimal disruption.
  • Change-driven updates: reads delta specs from openspec/changes/<name>/specs and writes to openspec/specs, creating main specs when they do not exist.
  • Safe, idempotent operations: can be executed multiple times with consistent results and preserves unrelated content.

Quick Start

Execute the merge operation by selecting a delta change and letting the tool apply its changes 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 specifications into main specs safely?

To merge delta specifications safely, the tool reads changes from openspec/changes/<name>/specs and applies added, modified, removed, and renamed requirements to main specs under openspec/specs, preserving unrelated content and ensuring updates do not lose existing work.

What happens to main specs when a delta spec adds or modifies requirements?

When delta specs add or modify requirements, the merge operation updates existing main specs under openspec/specs with the new values. If the target main spec does not exist yet, the tool automatically creates it to capture the updated requirements.

Can I run the same spec merge operation multiple times without causing conflicts?

Yes, the spec merge operation is idempotent. You can execute it multiple times with consistent results, and it will preserve unrelated content while safely applying the delta changes to the main specifications.

How does the merge process handle missing target specs or naming conflicts?

If deeper clarification is needed during the merge, the tool prompts you for the change name. It gracefully handles missing target specs by creating them and manages conflicts by intelligently merging renamed, modified, or removed requirements without disrupting existing work.

Do I need any external dependencies to sync openspec delta specifications?

No external dependencies are required to sync openspec delta specifications. The tool operates directly on your openspec directory structure, reading from the changes folder and writing updates to the main specs folder without needing additional packages.