openspec-sync-specs

Merge incremental OpenSpec changes into the main specification.

10.2k|702|Updated Apr 12, 2012
One-click install
npx skills add https://github.com/studyzy/imewlconverter --skill openspec-sync-specs-studyzy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/studyzy/imewlconverter/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/studyzy/imewlconverter --skill openspec-sync-specs-studyzy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams synchronize incremental changes into the main OpenSpec specification, enabling targeted updates without archiving entire changes.

Core Features & Use Cases

  • Incremental to main merge: Reads incremental specs under openspec/changes/<name>/specs and applies changes to the corresponding main spec, creating it if missing.
  • Controlled merging: Applies ADDED, MODIFIED, REMOVED, and RENAMED sections while preserving unrelated content.
  • Use Case: A product team submits an incremental spec to adjust a capability; this Skill merges the changes into the primary spec while keeping existing scenarios intact.

Quick Start

Use the openspec-cn tool to sync incremental specs into the main specification. Start by listing available changes with openspec-cn list --json, then select a change name so the agent can apply the corresponding specs to the main document.

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 incremental specification changes into a main spec?

To merge incremental specification changes, this Skill reads changes organized by capability and applies ADDED, MODIFIED, REMOVED, and RENAMED requirements to the main spec. It preserves existing content not mentioned by the increments while ensuring idempotent application.

What is the best way to sync OpenSpec incremental changes without archiving everything?

Syncing OpenSpec incremental changes without archiving is done by reading incremental specs and merging them into the main specification. This allows targeted updates to capabilities while keeping unrelated existing scenarios intact.

How do I apply ADDED, MODIFIED, and REMOVED requirements to an existing specification?

Applying ADDED, MODIFIED, and REMOVED requirements is handled through a controlled merging process. The Skill reads both incremental and main specs, applying changes section by section and prompting when needed to ensure accurate synchronization.

Can I synchronize capability changes if the main specification file is missing?

You can synchronize capability changes even if the main specification is missing. The Skill reads the incremental specs and creates the corresponding main spec automatically during the merge process if it does not already exist.

Does merging incremental specs overwrite unrelated content in the main document?

Merging incremental specs does not overwrite unrelated content. The process applies only the specified ADDED, MODIFIED, REMOVED, and RENAMED sections while explicitly preserving existing content not mentioned by the increments.

How to list available OpenSpec changes before merging them into the main specification?

To list available OpenSpec changes before merging, use the openspec-cn tool with the list --json command. This outputs available change names so you can select one for the agent to apply to the main document.