spectra-sync

Merge delta specs into main specs with idempotent updates.

45|3|Updated Jan 20, 2026

Search Tags:#automation #workflow #spectra #main-specs #spec-merging #delta-sync

Ready to run

npx skills add https://github.com/YuDefine/nuxt-supabase-starter --skill spectra-sync

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spectra-sync
Source: https://github.com/YuDefine/nuxt-supabase-starter/tree/main/.claude/skills/spectra-sync
Command: npx skills add https://github.com/YuDefine/nuxt-supabase-starter --skill spectra-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync delta specs from a change into the main specs to ensure consistent, automated merges and reduce manual conflict resolution.

Core Features & Use Cases

Agent-driven merging of delta specs into main specs using defined delta formats (ADDED, MODIFIED, REMOVED, RENAMED).
Guarded, idempotent updates that preserve content not mentioned in deltas.
Use cases include maintaining OpenSpec baselines during collaboration and incremental spec maintenance.

Quick Start

Specify the delta change name after /spectra-sync to apply the delta specs to the main specs.

Frequently Asked Questions about spectra-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate merging delta specs into main specs?▼

To automate merging delta specs, you can use an agent-driven workflow that reads both delta and main specs before applying updates. This ensures changes are integrated consistently while preserving existing content and enforcing idempotent updates.

What is a delta spec and when do I need to sync it?▼

A delta spec represents incremental changes like ADDED, MODIFIED, REMOVED, or RENAMED requirements for individual capabilities. You need to sync it into main specs to maintain consistent baselines during collaboration and reduce manual conflict resolution.

Does spec merging preserve existing content not mentioned in the deltas?▼

Yes, guarded and idempotent spec merging preserves existing content not mentioned in deltas. The workflow reads both documents and only applies the defined delta changes, prompting for clarification when the delta is ambiguous.

How do I apply delta changes to OpenSpec baselines?▼

To apply delta changes to OpenSpec baselines, specify the delta change name after the sync command. The agent-driven workflow then reads both specs and integrates the ADDED, MODIFIED, REMOVED, and RENAMED requirements automatically.

What happens when a delta spec is ambiguous during merging?▼

When a delta spec is ambiguous during merging, the workflow prompts for clarification. This agent-driven approach ensures that updates are applied correctly and consistently without guessing the intended changes.

Can I use automated spec merging for incremental spec maintenance?▼

Yes, automated spec merging is designed for incremental spec maintenance. It applies guarded, idempotent updates to ensure changes are integrated consistently into the main specs without overwriting unrelated existing content.