openspec-sync-specs

Merge delta specification changes into main OpenSpec spec files.

Updated May 5, 2022
One-click install
npx skills add https://github.com/BlackBeltTechnology/judo-runtime-core --skill openspec-sync-specs-blackbelttechnology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/BlackBeltTechnology/judo-runtime-core/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/BlackBeltTechnology/judo-runtime-core --skill openspec-sync-specs-blackbelttechnology

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of updating main specifications with changes from delta specifications, ensuring consistency without archiving the change prematurely.

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 edits main specs based on delta spec instructions, allowing for nuanced updates like adding specific scenarios.
  • Use Case: A developer has made changes to a feature's requirements in a delta spec. This Skill allows them to integrate those specific changes (e.g., adding a new test scenario) into the main specification without overwriting other existing content.

Quick Start

Use the openspec sync specs skill to update main specs with changes from the 'feature-enhancement' change.

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 specifications into the main spec repository?

To merge delta specifications into the main spec repository, synchronize changes from the delta files to update main specs, handling requirement additions, modifications, removals, and renames within specific capabilities.

What is the best way to update a main specification without archiving the change prematurely?

The best way to update a main specification without archiving the change prematurely is to synchronize delta specs into the main repository, allowing the change to remain active while ensuring spec consistency.

Do I need the openspec CLI to sync requirement modifications?

Yes, you need the openspec CLI to sync requirement modifications, as the synchronization process requires the CLI for listing and processing changes before updating the main specification files.

Can I add specific test scenarios to a main spec without overwriting existing content?

Yes, you can add specific test scenarios to a main spec without overwriting existing content by applying agent-driven edits that intelligently update main specs based on delta spec instructions.

How does synchronizing specs handle requirement renames and removals?

Synchronizing specs handles requirement renames and removals by intelligently merging delta specifications into main specification files, accurately processing modifications and deletions within specific capabilities.

What limitations exist when applying delta changes to capability specifications?

A key limitation when applying delta changes to capability specifications is that the operation strictly targets files within openspec/changes to update openspec/specs, requiring the openspec CLI for processing.