openspec-sync-specs

Merge delta specs into main specs while preserving existing content.

26|1|Updated May 2, 2022
One-click install
npx skills add https://github.com/anssip/passlane --skill openspec-sync-specs-anssip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/anssip/passlane/tree/main/.pi/skills/openspec-sync-specs
Command: npx skills add https://github.com/anssip/passlane --skill openspec-sync-specs-anssip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs often diverge from the main specifications; this Skill provides an agent-driven workflow to merge delta changes back into the canonical specs while preserving existing content.

Core Features & Use Cases

  • Agent-driven operation that reads delta specs and directly edits main specs to apply changes with intelligent merging.
  • Input handling prompts for a change name when omitted or ambiguous, avoiding guesswork.
  • Delta-driven updates support ADDED, MODIFIED, REMOVED, and RENAMED changes with preservation of existing scenarios.
  • Summarized output after processing to clearly communicate updated capabilities and applied changes.

Quick Start

Run openspec list --json to identify available delta specs and then apply them to the main 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 specs without losing existing content?

You can merge delta specs by running openspec list --json to identify available delta specs, then applying them to main specs. The skill prompts for a change name if omitted or ambiguous to ensure accurate merging.

What changes are supported when merging delta specs into main specifications?

Delta spec merging supports ADDED, MODIFIED, REMOVED, and RENAMED changes, preserving existing scenarios while applying controlled updates. After processing, it emits a summary of updated capabilities and applied changes.

Do I need to provide a change name before merging delta specs?

You do not need to provide a change name upfront; the workflow validates inputs and prompts for a missing or ambiguous change name during the merge process to avoid guesswork and ensure accurate spec updates.

What is the best way to apply controlled changes to canonical specifications?

The best way to apply controlled changes is using an agent-driven workflow that orchestrates reads of delta specs, identifies changes, and directly edits main specs with intelligent merging rules to preserve existing content.

How does delta spec management handle divergence from main specifications?

Delta spec management handles divergence by reading delta specs, identifying the specific changes, and merging them back into canonical specs with preservation of existing scenarios, ensuring the main specs remain the single source of truth.