openspec-sync-specs

Merges delta specifications into the main OpenSpec repository.

208|148|Updated Oct 27, 2021
One-click install
npx skills add https://github.com/elastic/terraform-provider-elasticstack --skill openspec-sync-specs-elastic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/elastic/terraform-provider-elasticstack/tree/main/.agents/skills/openspec-sync-specs
Command: npx skills add https://github.com/elastic/terraform-provider-elasticstack --skill openspec-sync-specs-elastic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync delta specs from a change to main specs.

Core Features & Use Cases

  • Agent-driven merge: read delta specs and apply changes to main specs, enabling coordinated updates.
  • Intelligent merging: supports ADDED, MODIFIED, REMOVED, and RENAMED requirements while preserving unrelated content.
  • Use Case: when delta specs exist for a feature, merge them into the corresponding main spec to keep the source of truth up to date without archiving the delta.

Quick Start

Run the openspec-sync-specs operation to merge delta specs into the main specifications by applying delta changes to openspec/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 merge delta specs into main OpenSpec specifications?

To merge delta specs into main OpenSpec specifications, apply changes from delta specs located under openspec/changes/<name>/specs to the target main specs in openspec/specs, automatically creating new specs if the target does not exist.

What is delta spec management in OpenSpec?

Delta spec management in OpenSpec is the process of applying incremental specification changes—ADDED, MODIFIED, REMOVED, and RENAMED requirements—from a feature branch to the main repository to keep the source of truth up to date.

Does merging OpenSpec delta specs preserve unrelated content in the main spec?

Merging OpenSpec delta specs preserves unrelated content in the main spec by only applying the specific ADDED, MODIFIED, REMOVED, and RENAMED requirements defined in the delta, leaving all other existing sections untouched.

When do I need to sync delta specs to main specs?

You need to sync delta specs to main specs when delta specs exist under openspec/changes/<name>/specs and you want to merge these coordinated updates into the main specification source of truth without archiving the delta.

What happens if a target main spec does not exist during an OpenSpec merge?

If the target main spec does not exist under openspec/specs during an OpenSpec merge, the operation automatically creates a new main spec to apply the delta changes to.

What is the best way to automate spec updates for OpenSpec changes?

The best way to automate spec updates for OpenSpec changes is using an agent-driven merge operation that reads delta specs and applies ADDED, MODIFIED, REMOVED, and RENAMED requirements to the main specs, outputting a concise update summary.