openspec-sync-specs

Merge delta requirement specs into main OpenSpec specification files.

18|3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/igamenovoer/houmao --skill openspec-sync-specs-igamenovoer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/igamenovoer/houmao/tree/main/tests/fixtures/plain-agent-def/skills/openspec-sync-specs
Command: npx skills add https://github.com/igamenovoer/houmao --skill openspec-sync-specs-igamenovoer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of keeping your main OpenSpec requirements up to date when you have delta changes that should be merged, without archiving the delta.

Core Features & Use Cases

  • Delta-to-main merging: Reads delta spec files and applies added, modified, removed, and renamed requirements to the corresponding main spec files.
  • Capability-aware updates: Updates existing capability specs or creates new main spec files when a capability doesn’t exist yet.
  • Guardrailed, idempotent operation: Preserves content not mentioned in the delta and provides a clear summary of what changed.

Quick Start

Tell the AI to sync the delta spec changes named "my-feature-change" into the corresponding main OpenSpec specifications.

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 requirement specs into main OpenSpec specifications?

Yes, capability-aware updates create missing main spec files for new capabilities while preserving unrelated content in existing ones, ensuring only intended capability-level updates are applied during synchronization.

What is the best way to synchronize spec changes without archiving the delta branch?

Omitting the change name triggers the Skill to list available changes via 'openspec list --json', allowing you to identify and select the specific delta branch spec modifications to merge into the main specifications.

Does spec synchronization preserve unrelated content in main capability specs?

The Skill produces an end summary detailing the exact capabilities updated and the specific operations performed, providing a clear audit trail of the spec synchronization for compliance documentation.

How do I apply adds, modifications, removals, and renames from a delta spec to main specs?

No additional dependencies are required. The Skill operates independently by reading delta files from 'openspec/changes/' and main specs from 'openspec/specs/' to execute the capability-level updates.