openspec-sync-specs

Merge delta specification changes into main OpenSpec specification documents.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/nuitsjp/teams-board --skill openspec-sync-specs-nuitsjp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/nuitsjp/teams-board/tree/main/.rulesync/skills/openspec-sync-specs
Command: npx skills add https://github.com/nuitsjp/teams-board --skill openspec-sync-specs-nuitsjp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of updating main specification documents with changes defined in delta specification files, ensuring consistency and efficient management of evolving requirements.

Core Features & Use Cases

  • Intelligent Merging: Applies changes from delta specs to main specs, handling additions, modifications, removals, and renames of requirements.
  • Agent-Driven Operation: The AI directly reads and edits specification files, allowing for nuanced merging without full file replacements.
  • Use Case: When a new feature is developed, its requirements are documented in a delta spec. This Skill integrates those new requirements into the main specification document, preserving existing content.

Quick Start

Use the openspec-sync-specs skill to sync changes from the 'new-feature-v1' change 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 sync delta specs to main specs in software development?

You can sync delta specs to main specs by using a tool that intelligently merges added, modified, removed, and renamed requirements from your delta files directly into your main specification documents. This ensures consistency without replacing the entire file.

What is intelligent merging for specification requirements?

Intelligent merging for specification requirements is the process of applying changes from delta specification files into main specification documents. It handles additions, modifications, removals, and renames while preserving existing content within the main specs.

How do I merge added and modified requirements without losing existing spec content?

You can merge added and modified requirements without losing existing content by using an agent-driven operation that directly reads and edits the specification files. This allows for nuanced merging of delta specs into main specs rather than full file replacements.

When do I need to synchronize delta specification files?

You need to synchronize delta specification files when a new feature is developed and its requirements are documented in a delta spec. This process integrates those new requirements into the main specification document to maintain evolving requirement consistency.

What directory structure is required for merging openspec delta files?

The required directory structure for merging openspec delta files involves operating on files within the openspec/changes/<name>/specs/ directory for deltas and the openspec/specs/<capability>/ directory for main specification documents.

Can I automate updating main specification documents with evolving requirements?

Yes, you can automate updating main specification documents with evolving requirements by synchronizing delta specification files into the main specs. This automates the intelligent merging of changes across capabilities, ensuring efficient management of evolving requirements.