openspec-sync-specs

Merge delta specification changes into main openspec documents.

133|23|Updated Mar 23, 2020
One-click install
npx skills add https://github.com/aehrc/pathling --skill openspec-sync-specs-aehrc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/aehrc/pathling/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/aehrc/pathling --skill openspec-sync-specs-aehrc

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

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

Core Features & Use Cases

  • Intelligent Merging: Applies additions, modifications, removals, and renames of requirements intelligently, preserving existing content.
  • Agent-Driven Operation: The AI directly edits specification files, enabling nuanced merging without manual intervention.
  • Use Case: When a new feature is developed, its requirements are documented in a delta spec. This Skill applies those changes to the main specification, updating documentation seamlessly.

Quick Start

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

To merge delta specification files into main specification documents, you use an automated sync process that intelligently applies added, modified, removed, and renamed requirements. This ensures your main specs reflect the latest changes while preserving existing content.

What is the best way to synchronize requirements across feature branches?

Synchronizing requirements across feature branches is best handled by an agent-driven operation that directly edits specification files. This enables nuanced merging of delta specs into main specifications, ensuring documentation updates seamlessly without manual intervention.

Do I need the openspec CLI to sync delta specs?

Yes, you need the openspec CLI installed to sync delta specs. The CLI is required for listing and managing changes, allowing the synchronization process to accurately identify and apply modifications to the main specification documents.

Can I automate updating main specifications when new features are developed?

You can automate updating main specifications when new features are developed by documenting requirements in a delta spec. The sync tool then applies these changes to the main specification, updating your documentation automatically and efficiently.

How does intelligent merging handle removed and renamed requirements?

Intelligent merging handles removed and renamed requirements by accurately identifying these changes within delta specs and applying them to main specification documents. This preserves existing valid content while ensuring outdated or renamed requirements are correctly updated.

What are the limitations of agent-driven specification merging?

The primary limitation of agent-driven specification merging is its strict dependency on the openspec CLI for listing and managing changes. Without the CLI environment properly configured, the synchronization process cannot identify or apply delta spec modifications.