openspec-sync-specs

Merge delta specification changes into OpenSpec main spec files.

4|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/JanuaryLabs/deepagents --skill openspec-sync-specs-januarylabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/JanuaryLabs/deepagents/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/JanuaryLabs/deepagents --skill openspec-sync-specs-januarylabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the manual, error-prone task of applying focused specification changes from delta files into the canonical OpenSpec main specs, reducing repetition and preserving unrelated content while ensuring clear, auditable updates.

Core Features & Use Cases

  • Agent-driven intelligent merging: Reads ADDED, MODIFIED, REMOVED, and RENAMED sections in delta specs and applies targeted updates to main spec files without wholesale replacement.
  • Capability-aware file handling: Creates new capability spec files when needed, preserves existing scenarios not mentioned in deltas, and renames or removes requirement blocks as specified.
  • User confirmation and summaries: Prompts the user to select ambiguous changes, shows diffs of edits, and produces a concise summary of added, modified, removed, and renamed requirements.
  • Use Case: When a change branch introduces a new scenario or requirement tweak, run this Skill to merge those deltas into openspec/specs/* while keeping unrelated content intact.

Quick Start

Use the openspec-sync-specs skill to sync the 'change-name' delta into main specs and show a summary of added, modified, removed, and renamed requirements.

Frequently Asked Questions about openspec-sync-specs

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

FAQPage Schema
How do I sync delta specs into main OpenSpec spec files?

To sync delta specs, use a tool that reads ADDED, MODIFIED, REMOVED, and RENAMED sections from delta files and intelligently merges them into existing main OpenSpec spec files while preserving unrelated content.

Can I merge specification changes without overwriting unrelated scenarios?

Yes, intelligent idempotent merging applies targeted updates to specification files without wholesale replacement, preserving existing scenarios and requirements that are not mentioned in the delta changes.

Does OpenSpec sync require the openspec CLI to apply changes?

Yes, applying delta specification changes requires the openspec CLI. The tool reads delta files and existing main specs to perform intelligent merges and output a summary of applied changes.

What's the best way to handle renamed or removed requirements in spec files?

The best way is to use a capability-aware sync tool that reads RENAMED and REMOVED sections from delta specs to rename or remove requirement blocks in main spec files automatically.

How does capability-aware file handling work when syncing new specifications?

Capability-aware file handling creates new capability spec files when needed during the sync process, ensuring new requirements from delta files are properly organized within the OpenSpec directory structure.

What happens when multiple delta changes are available but none is specified?

When a specific change is not provided, the tool prompts the user to select which delta to apply, ensuring clear and auditable updates to the main specification files.