openspec-sync-specs

Synchronize delta specification files into main specification files using the openspec CLI.

9|1|Updated Jun 6, 2018
One-click install
npx skills add https://github.com/edwardsnjd/dot-files --skill openspec-sync-specs-edwardsnjd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/edwardsnjd/dot-files/tree/main/configuration/agents/.agents/skills/openspec-sync-specs
Command: npx skills add https://github.com/edwardsnjd/dot-files --skill openspec-sync-specs-edwardsnjd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of updating main specification files with changes defined in delta specification files, ensuring consistency and efficient management of evolving requirements.

Core Features & Use Cases

  • Intelligent Merging: Applies changes from delta specs to main specs, handling additions, modifications, removals, and renames of requirements intelligently.
  • Agent-Driven Operation: Operates as an agent, directly editing main specs based on delta spec content.
  • Use Case: When a new feature is being developed, its requirements can be tracked in a delta spec. This Skill allows those changes to be seamlessly integrated into the main specification without manual copying or complex merging.

Quick Start

Use the openspec-sync-specs skill to sync changes from the 'new-feature-branch' 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 sync delta specification files into main specs?

To sync delta specifications into main specs, you apply changes from delta files to merge additions, modifications, removals, and renames of requirements intelligently. This ensures consistency when managing evolving requirements across capabilities.

How does intelligent merging of requirement changes work?

Intelligent merging applies delta spec content to directly edit main specs, handling requirement additions, modifications, removals, and renames. This automated process avoids manual copying and ensures consistent specification updates.

Do I need the openspec CLI to synchronize specification changes?

Yes, you need the openspec CLI to synchronize specification changes. The CLI is required for listing and managing changes before applying delta spec updates to the main specification files.

What is the best way to manage evolving requirements during feature development?

Managing evolving requirements is best done by tracking new feature changes in a delta spec. You then synchronize these delta specs into main specification files to seamlessly integrate updates without complex manual merging.

Can I use this approach to rename requirements within specified capabilities?

Yes, you can rename requirements within specified capabilities. The synchronization process handles renames alongside additions, modifications, and removals when applying delta specification changes to the main files.

Why are my main specification files not updating with new feature changes?

Main specification files fail to update when delta specs are not properly synchronized. You must run the synchronization process to apply delta changes, ensuring the openspec CLI is used to list and manage the pending changes.