openspec-sync-specs SKILL.md skillA

This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.

openspec-sync-specs from muthuishere/toolnexus is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add muthuishere/toolnexus/openspec-sync-specs@v1.0

Pins v1.0 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

muthuishere/toolnexus

Path

.claude/skills/openspec-sync-specs/SKILL.md

Versions recorded

1

Latest version

v1.0, committed Jun 26, 2026

Size

4,787 bytes

Repository stars

6

License

MIT

Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

Sync delta specs from a change to main specs.

This is an **agent-driven** operation - you will read delta specs and directly edit main specs to apply the changes. This allows intelligent merging (e.g., adding a scenario without copying the entire requirement).

**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.

**Steps**

1. **If no change name provided, prompt for selection**

   Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.

   Show changes that have delta specs (under `specs/` directory).

   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.

2. **Resolve change context**

   Run:
   ```bash
   openspec status --change "<name>" --json
   ```

   If status reports `actionContext.mode: "workspace-planning"`, explain that workspace spec sync is not supported in this slice and STOP. Do not fall back to repo-local paths or edit linked repos.

3. **Find delta specs**

   Use `artifactPaths.specs.existingOutputPaths` from the status JSON as the list of delta spec files.
…

Read the whole file at its exact version.

How to install

mdr add muthuishere/toolnexus/openspec-sync-specs@sha256:9c74dad096467f98

[![mdr](https://markdownregistry.com/badge/art_nn6a7gxzxvx5pivr.svg)](https://markdownregistry.com/a/art_nn6a7gxzxvx5pivr)

Versions

The registry has recorded 1 version of this file, committed on Jun 26, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_nn6a7gxzxvx5pivr
GET https://markdownregistry.com/api/v1/resolve?ref=muthuishere/toolnexus/openspec-sync-specs
GET https://markdownregistry.com/api/v1/blob/9c74dad096467f982806ccf33e213f459890e0b79af1f69f6e9f1e790bb2fccf

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from muthuishere/toolnexus

Every file in muthuishere/toolnexus

Other files named openspec-sync-specs

Browse by kind, by grade A, or by owner.