skills.rest
echowaves
echowavesOFFICIAL
Explore all skills by this author →
WebsiteGitHub

openspec-sync-specs

Merge delta requirement blocks into main specification files.

Updated Feb 12, 2021
Search Tags:#documentation automation#requirements management#openspec#spec synchronization#intelligent merging#idempotent workflows
One-click install
npx skills add https://github.com/echowaves/WiSaw.cdk --skill openspec-sync-specs-echowaves
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/echowaves/WiSaw.cdk/tree/main/.roo/skills/openspec-sync-specs
Command: npx skills add https://github.com/echowaves/WiSaw.cdk --skill openspec-sync-specs-echowaves

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of keeping your requirement documentation up to date by syncing changes made in delta specs back into the corresponding main specs without losing unrelated content.

Core Features & Use Cases

  • Delta-to-main intelligent merging: Applies added, modified, removed, and renamed requirement blocks from change-specific delta specs into the main spec files while preserving anything not mentioned in the delta.
  • Capability-aware updates: Updates existing capability specs or creates new main spec files when a capability does not yet exist.
  • Guardrailed, idempotent workflow: Prompts the user to choose a change when the change name is missing or ambiguous, and stops safely when no delta specs are found.

Quick Start

Ask to sync delta specs into main specs by providing the desired change name, or ask the assistant to infer it from your context if you did not specify one.

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 specifications into main spec files?▼

To merge delta requirement specifications, apply added, modified, removed, and renamed requirement blocks from delta specs into main spec files. This synchronization process updates capabilities while preserving any unspecified content in the original documents.

What is the best way to synchronize requirement changes without archiving the delta?▼

Synchronizing requirement changes without archiving the delta involves applying partial updates from the active delta spec into the main repository. This maintains the delta spec separately while ensuring the main specs reflect the latest modifications.

How do I update main requirement specs while preserving unrelated content?▼

Updating main requirement specs while preserving unrelated content is achieved through intelligent merging. The system applies only the specified changes from the delta spec, ensuring any content not mentioned in the delta remains untouched in the main files.

Do I need to specify a change name to sync requirement specs?▼

You do not need to specify a change name if the system can infer it from your context. When a change name is missing or ambiguous, the workflow prompts you to select the correct change explicitly before proceeding with the synchronization.

What happens if no delta specs are found during spec synchronization?▼

If no delta specs are found during spec synchronization, the idempotent workflow stops safely. This guardrailed mechanism prevents errors by halting the process when there are no available changes to merge into the main specifications.

Related Skills

Explore More Software Engineering Skills→
igamenovoerigamenovoer
18

openspec-sync-specs

Merge delta requirement specs into main OpenSpec specification files.

Community
Intermediate
caelaxiecaelaxie

openspec-sync-specs

Merge delta specification changes into main markdown spec files.

Community
Intermediate
TranVanTienDatTranVanTienDat

openspec-sync-specs

Sync delta specifications to main specifications using the openspec CLI.

Community
Advanced
cenmiaocenmiao

openspec-sync-specs

Merge delta spec changes into main specification files.

Community
Advanced