Sync Delta Spec

VerifiedCaution

Merge a change's delta spec into the domain spec source of truth without archiving.

Sby Skills Guide Bot
DevelopmentIntermediate
7/22/2026
Claude Code
#spec-management#delta-spec#merge#source-of-truth#workflow

Recommended for

Automated summary

Merges an active change's delta spec into the domain spec source of truth without archiving the change.

Strengths

  • Runs validation before applying the delta, so inconsistent specs are caught by spec_state rather than merged blindly
  • Repeatable and idempotent: each run re-applies the current delta while keeping the change folder active
  • Reports concretely which requirements were added, modified, removed or renamed
  • No task gate, so it can be run at any point in the change lifecycle

Limitations

  • Assumes the repo has the agents.lib.spec_state module and a working .venv
  • Does not describe any conflict resolution if the domain spec has diverged from the delta
  • Does not finalize the change; /archive is still required afterwards
When to use it

Use it when a delta spec needs to land in the domain spec before the change is finished, for instance to share validated requirements early.

When not to use it

Don't use it to close out a change or clean up its folder — that is what /archive is for.

Security analysis

Caution
Quality score84/100

The skill runs local Python commands to inspect, validate, and merge spec deltas. There is no network exfiltration, obfuscation, or obviously destructive command, but it does use shell execution with an unquoted user argument and writes to a source-of-truth file, so it warrants caution rather than a clean safe rating.

Findings
  • •User-supplied `{slug}` is interpolated into shell commands without quoting or validation; a slug containing shell metacharacters could lead to unintended command execution.
  • •The skill requires Bash/local Python execution but declares no allowed-tools restriction, so the agent's shell use is not constrained by the skill metadata.
  • •`apply --write` mutates the domain spec source of truth and is repeatable; this is intended but could propagate mistakes without a confirmation or rollback step.
How this analysis is made

Examples

Sync a specific change
/sync add-user-auth
Sync then report the diff
Run /sync for the slug `billing-limits` and then summarize which requirements were added, modified, removed or renamed in the domain spec.
Re-apply after editing the delta
I updated the delta spec for `search-filters`. Run /sync search-filters again to re-apply it to the domain spec and tell me what changed.

name: sync description: Merge delta spec into the domain spec source of truth argument-hint: "<slug>" disable-model-invocation: false

Sync

Merge a change's delta spec into the domain spec source of truth without archiving. The change folder remains active.

Setup

Parse $ARGUMENTS:

  • slug (required)

Process

  1. Read the delta:
    .venv/bin/python -m agents.lib.spec_state show-change {slug}
    
  2. Validate delta against domain spec:
    .venv/bin/python -m agents.lib.spec_state validate --change {slug}
    
  3. Apply delta (merge into domain spec):
    .venv/bin/python -m agents.lib.spec_state apply {slug} --write
    
  4. Report what changed (requirements added, modified, removed, renamed)

Notes

  • No task gate — sync does not check tasks.md completion. Can sync at any time.
  • Repeatable — unlike archive, sync can be run multiple times. Each run re-applies the current delta.
  • Change folder remains active — not archived. Use /archive to finalize.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/sync-delta-spec-mrwak9h9/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/sync-delta-spec-mrwak9h9' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/sync-delta-spec-mrwak9h9/download' --output '.skill-downloads/sync-delta-spec-mrwak9h9/SKILL.md.part' && mv '.skill-downloads/sync-delta-spec-mrwak9h9/SKILL.md.part' '.skill-downloads/sync-delta-spec-mrwak9h9/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Original excerpt: Setup

Parse $ARGUMENTS:

  • slug (required)

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/sync-delta-spec-mrwak9h9/SKILL.md' && test -s '.skill-downloads/sync-delta-spec-mrwak9h9/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/sync' && cp -R '.skill-downloads/sync-delta-spec-mrwak9h9' '.claude/skills/sync'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/sync-delta-spec-mrwak9h9'

openskills read 'sync-delta-spec-mrwak9h9'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/sync-delta-spec-mrwak9h9/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills