openspec-sync-specs

Merge delta specifications into main specs with idempotent updates.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/garethbaumgart/mental-metal --skill openspec-sync-specs-garethbaumgart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/garethbaumgart/mental-metal/tree/main/.cursor/skills/openspec-sync-specs
Command: npx skills add https://github.com/garethbaumgart/mental-metal --skill openspec-sync-specs-garethbaumgart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs often diverge from main specs, requiring manual, error-prone merges. This skill automates synchronization by applying delta changes to main specs while preserving existing content.

Core Features & Use Cases

  • Intelligent merging of ADDED, MODIFIED, REMOVED, and RENAMED requirements between delta and main specs
  • Safe, idempotent updates that can create main specs when missing
  • Clear traceability of changes applied to maintain audit history

Quick Start

Run the delta sync command to merge changes from openspec/changes into openspec/specs and verify the result.

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 specs into main specs automatically?

You can merge delta specs into main specs automatically by running a delta sync command that applies ADDED, MODIFIED, REMOVED, and RENAMED changes from openspec/changes directly into openspec/specs while preserving existing content.

What is delta specification synchronization in OpenSpec?

Delta specification synchronization is the automated process of applying incremental changes from delta specs to main specs, ensuring that divergent requirements are merged safely without overwriting existing content.

Can I create new main specs automatically when merging delta changes?

Yes, merging delta changes can automatically create new main specs when they are missing, ensuring safe and idempotent updates while maintaining clear traceability of applied changes.

What is the best way to handle REMOVED and RENAMED requirements in spec synchronization?

The best way to handle REMOVED and RENAMED requirements is using intelligent delta merging, which automatically applies these specific change rules to update main specs accurately without manual intervention.

Why does manual delta spec merging cause errors?

Manual delta spec merging causes errors because delta specs often diverge from main specs over time, making manual synchronization prone to mistakes that automated merging eliminates through idempotent updates.

Are OpenSpec delta sync updates idempotent and safe for existing content?

Yes, OpenSpec delta sync updates are idempotent and safe, meaning applying the same delta changes multiple times yields the same result without destroying or duplicating existing main spec content.